Re: FrontPage Extensions - are they worth it?

From: Kevin Spencer (kevin_at_DIESPAMMERSDIEtakempis.com)
Date: 01/24/05 

Date: Mon, 24 Jan 2005 08:49:22 -0500

Whoa, Andrew! While FrontPage server extensions do perform functionality in
all of the areas you mentioned, your reply implies that without them none of
these things can be done, which just ain't so. Here's a sub-list of the
things you CAN'T do without FrontPage server extensions:

FrontPage Include HTML (ASP server-side includes are fine without server
extensions)
Shared Borders
FrontPage Themes
Dynamic Web Templates

You CAN do all kinds of form handlers using server-side scripting, as well
as doing SharePoint Development using Visual Studio and SharePoint web
interfaces, database-driven sites using server-side technologies and/or
scripting, Site Search Engine, as well as any number of other types of
search engines, in fact, just about anything that isn't a FrontPage-related
functionality. 

-- 
HTH,
Kevin Spencer
Microsoft MVP
.Net Developer
Neither a follower nor a lender be.
"Andrew Murray" <admurray@iinet.net.au> wrote in message 
news:u0j68NhAFHA.4044@TK2MSFTNGP11.phx.gbl...
> You would be missing quite a bit from not using frontpage extensions.
>
> In a nutshell, some of the FP features to use frontpage extensions include
>
> Include Pages
> Shared Borders
> Formtoemail submission
> Database driven sites
> Sharepoint services  (although this is also independent of FP, FP makes 
> some use of Sharepoint in its features)
> Dynamic templates
> Site-search engine
>
> to name but a few.
>
> However, it is the individual's choice.   Anything you want to do such as 
> send an email from an HTML form can be done with third party scripts. 
> Basically anything FP offers can be done with other scripts (search 
> engines, include pages, form submission, database content etc - Frontpage 
> can do all or most of these in its own right.).
>
>
> If you publish to a server with extensions, you need to publish by 
> frontpage http:// mode (look up Help in FP for further info).
>
>
>
>
> "Rich" <Rich@discussions.microsoft.com> wrote in message 
> news:B2277040-3C06-4A1D-A08C-CCE0AC4EFE24@microsoft.com...
>> I've just created a new domain and the basic hosting package I will use 
>> does
>> not support FrontPage extensions. If I choose this package what I am 
>> losing
>> in terms of FrontPage functionality?
>>
>> Also I will need to upload my current website that does have Extensions 
>> to
>> the new domain. Are there any files I need to exclude if I go for the 
>> basic
>> package?
>>
>> -- 
>> Rich
>
>

Relevant Pages

  • Re: Server Extensions Administrator
    ... To avoid the error in FrontPage, you must open the web in FrontPage, ... http://machine:8080 as the web address then the extensions are ... Try running server health, and see if that makes a difference. ... At this point I am at the limit of my knowledge of installing ...
    (microsoft.public.frontpage.extensions.windowsnt)
  • Re: Server Extensions Administrator
    ... the extensions do not work. ... To avoid using a subweb set up a virtual server, ... FrontPage Support: http://www.frontpagemvps.com/ ... have not been installed - click Extend to install the extensions. ...
    (microsoft.public.frontpage.extensions.windowsnt)
  • Re: Server Extensions Administrator
    ... got error about extensions not loaded. ... I get the error (no server extensions) ... Either, Open the default web site in FrontPage, then create a subweb ... Ron Symonds - Microsoft MVP ...
    (microsoft.public.frontpage.extensions.windowsnt)
  • Re: front page 2003 running on small business server 2003 r2 issue
    ... Tick FrontPage 2002 Server Extensions ... > FrontPage will create sub webs in an existing web site that has FP ...
    (microsoft.public.frontpage.programming)
  • Re: Server Extensions Administrator
    ... extensions will not work ... Either, Open the default web site in FrontPage, then create a subweb ... or better, open IIS MMC and create a new server, and choose ... Otherwise, click Administration. ...
    (microsoft.public.frontpage.extensions.windowsnt)