I recently installed VS 2005 on my workstation and created a web-app which is working fine as a file-system application.  But, when I try to publish it to our web server it fails with an error message of "The Web server does not appear to have the FrontPage server extensions installed."  Which, of course, is true as we are not using FrontPage!  Others do not get this message and publish to this server just fine.  I have been trying to find some configuration item to turn off this requirement but have been unsuccessful so far.  I have found that FrontPage extensions are optional with VS 2005 web-apps and do not understand why I am blocked from publishing my app because of it.  Please help!

For some features to work is to install the FrontPage extension. Check below link for more information

http://msdn2.microsoft.com/en-us/library/z29sddxk(VS.71).aspx

HC 

Thanks!

 I am trying to find out which port the server uses  to FTP it over, but everone in the know is out for the holidays.  But the real question is why am I getting this?  The other two programmers in my office can both publish to this sever directly without getting this failure.   Apparently, there has to either be something in the VS configuration (which is not very intuitive) or I have used some control on my pages which is requiring FrontPage.  Since, our office does NOT intend to install FrontPage on the server, I must know why and how to avoid this requirement and publish directly.

FrontPage Extensions really have nothing to do with FrontPage. It is just hirtorical name. FPSE allow access to server content via http. You don't need to install FrontPage software on the server, FPSE are part of IIS setup options in Windows component setup.

I do not care whether FrontPage extensions have any relationship to the actual FrontPage product!  I do not care if there may be some advantages to having FrontPage extensions on the IIS server!  I do not care to be forced to use FTP to publish a web-app to the server when others VS configurations in my same shop do not have to contend with this problem.  I need to know, what it could be about my configuration or app that necessitates that there must be these extensions (and is different from the others using VS 2005) on this IIS server for my app to be published there, espcially when the documentation says they are supposed to be OPTIONAL!?    Please, someone answer my question and not side-step the issue.

Getting Desperate!

First, no one is "sidestepping" the issue.  FPSE is one of the solutions available for connecting to a website and for publishing.  Personally, I don't use it and don't want to use it.

Now, have you compared your VS configuration with the others who can publish to the web server?

Additionally, what type of access do you have to your web server?  Is it internal and can you map a drive to it?

If you are running Vista, it may be related to your access permission. Perhaps this thread may help: http://forums.asp.net/p/1069510/1645821.aspx

Tough, I am not running Vista (XP Pro workstation), access permissions were one of the things I considered, but would expect to get an access violation message.  I can map an F:  drive to the remote server and have copied my application to the directory created for it.  I can open the application on the F: drive in VS and it still runs fine, but only on the VS local host.  I can use IE 7 to access a "Hello World" index.asp page in the server directory using the external IP address URL I was given, but when I try to open my apps default.aspx or a "Hello World" index.aspx page in the same directory, I get "Server Application Unavailable" in big red letters.

Careered, says he doesn't use FrontPage extensions.  So tell me how to not use them.  From what I see VS has four options File System, local IIS, FTP and Remote Server.  Both File System and Local IIS work off of my workstation only.  I can't seem to get FTP to work as with what I think is the right port number, it just sits there perpetually trying to open the site and Remote Server (HTTP) seems to be synonymous with FrontPage extensions that I am told "WE DON'T USE".  I suspect we probably should have the extensions installed, but I do not control the server setup which is in another state. 

 Since the only other person here is able to "publish" to the server from VS 2005 without getting these extensions required messages, I am being told to uninstall and reinstall Visual Studio.  Somehow I think this is not my solution and will be wasting hours I can't afford.  There has to a VS configuration, web.config, or other setting that is causing this, but I am unable to find it. 

Though (not Tough) -- sorry!

Sorry for all the confusion.  It is looking more and more like it is a server security configuration problem.  The others who are able to publish to the server are doing so using their F: drive mapping via File System and not via the Remote Server HTTP address.  The sever fails to run several different apps already running there by changing their security roles setup similar to the ones my sites directory was provided.  We have some people looking at it.  I am curious why I cannot seem to locate the server in my Internet Services Manager, even when providing the server's IP address and a valid login, ISM says it can't find it.  But, that is another issue that someone else is going to have to resolve. 

I use the File System method for developing web applications.  When I published through VS 2005, I have a staging directory on my development web server that I am mapped to and is where I publish my production files.  From this server, I copy the files over to the production server.