ClickOnce: Installing FrontPage Server Extensions 2002 on IIS 6.0 for Publishing

In order to test some ClickOnce deployments today, I had to configure a new Web server to allow ClickOnce publishing through Visual Studio. ClickOnce deployments can be x-copied to a Web server, so not having that auto-publish capability is not the end of the world. However, after testing one of my ClickOnce applications 20 or so times in the span of a day, I grew well nigh sick and tired of copying over files.

This Microsoft TechNet article contained the special sauce I needed:

To add the FrontPage 2002 Server Extensions component


In the Windows Components Wizard select Application Server, and then click Details.


In the Application Server subcomponents list, select Internet Information Services, and then click Details.


In the IIS subcomponents list, select the check box for FrontPage 2002 Server Extensions, and then click OK to complete the Windows Components Wizard and install FrontPage 2002 Server Extensions. You might need your Windows Server 2003 installation CD to complete the installation.'s a little buried.

Comments (5)

  1. G.T says:

    Just so confusing, Microsoft is not recommending the front page server extensions at all, they are not compatible with SharePoint and it is not recommended to have them over an IIS that runs on Windows 2003, and they cannot be installed on the Visual Studio.NET Web Server.

    And after all of that, some developer at Microsoft just decides to go ahead and make then a requirement for Click Once Deployment.

    It just shows you how professional are some people there, and how much code reviews have been done on that product, they simply don’t care.

  2. Jay A. Allen says:

    Thanks for writing, G.T. Two points:

    (1) It’s not required for ClickOnce deployment. As I mentioned, xcopy deployment works perfectly.

    (2) All of the guidance I’ve seen says that SharePoint Team Services is a superset of FrontPage SE 2002, essentially replacing them. I haven’t found any documented conflicts. If you can send me a link to some docs which discuss this, that’d be great. Thanks!

  3. Jay A. Allen says:

    Also, VS supports publishing to a filesystem directory, even if the deployment occurs over HTTP. So you don’t need the FrontPage Server Extensions at all. In my experience, it’s better to steer clear of them anyway.

Skip to main content