Last post Dec 29, 2006 03:04 AM by George Ma - MSFT
Dec 22, 2006 08:50 AM|Chris Koystas|LINK
While trying to debug an ASP.NET application with Windows XP SP2 (fully updated), .NET Framework 1.1.4322, VS.NET 2003 Service Pack 1 and Internet Explorer 7.0 I receive the following message:
Error while trying to run project: Unable to start debugging on the web server. The server does not support debugging of ASP.NET or ATL Server applications. Click Help for more information on how to enable debugging. You may also want to refer to the ASP.NET
and ATL Server debugging topic in the online documentation.
This happens when I select Debug as the active configuration and "Wait for an external process to connect". From the .NET help I found out that the problem actually resides in the start page which belong to a frameset cause of the need for using my ActiveX
controls in pages since I want them to stay alive throughout the session (they control external client devices).
The problem is easily solved by changing the start action of the debug to "Start Project" then change the page to something else (e.g. a normal page) and then select again the "Wait for an external process to connect".
This should be completely unnesessary since I am not actually starting that page and the debugger is waiting for a client to call him.
The fact remains that this behaviour is wrong from the .NET side and the environment should not check start page on that particular start action when trying to start debugging and each time i want to change the mode I have to change back the page to the
original frameset which..... by the way... works just fine when I am debugging the application locally WITH the frameset page.
I don't know if this is the right place to post a bug/unwanted behaviour/"feature" but it's as good as any if someone can pass it to the right people.
For anyone that has come across the same problem... to circumvent the unwanted behaviour you only need to change the page to a web form and not a frameset. [:)] or manually attach to aspnet_wp.exe [;)]
This problem doesn't have anything to do with this link:
Also this doesn't have anything to do with my installation since the first thing I did was to re-register the aspnet on IIS.
Furthermore on VS.NET help there is a similar problem solution that also prompts the user to change the start page but it's for another reason and not that kind of debugging.
Dec 29, 2006 03:04 AM|George Ma - MSFT|LINK
If you have an XP Pro or W2K Pro machine, you may need to think about the order of installation between VS7 and IIS. If you install IIS after VS7, you will get this error. In this case, please register “aspnet_isapi.dll” with “aspnet_regiis.exe –i”.
Please check following article for more details.