I'm attempting to debug VB ASP.NET websites within IIS7 using VS2008 SP1 on Vista 64-bit Ultimate but getting the message "Unable to start debugging on the web server. IIS does not list a web site that matches the launched URL".
The next test was to run the website using the file system rather than IIS – that works, so it looks like an IIS7 config setting that is the problem.
So next I ran:
%systemroot%\system32\inetsrv\APPCMD list sites
To see if my test site was present – and it is.
I'm reasonably sure that debugging has worked in the past, but can't be absolutely sure because I've been doing WinForms stuff recently and websites on a Windows XP using VS2005 but not websites on Vista using VS2008. However for the Vista/VS2008 development I have installed .NET Framework 3.5 SP1 - so that may be a factor. Also I’ve installed the URL Rewrite module (though I did remove it temporarily whilst having these problems).
Apart from that I've done all the usual things like run in Administrator mode, enabled Windows Authentication, HTTP Keep Alives are enabled per http://ryanfarley.com/blog/archive/2005/08/23/8540.aspx.
The developer learning page at http://learn.iis.net/page.aspx/387/using-visual-studio-2008-with-iis-70/ goes through creating a website with VS2008 but this didn’t bring me any nearer a solution.
The page at http://msdn.microsoft.com/en-us/library/dwesw3ee(VS.80).aspx does not cover Vista and VS2008 (at this time) and there appear to be some material differences.
On VS2003 there used to be a webinfo file that ensured that the debugger could reference the project file, but that now seems obsolete.
What magic setting will finally persuade VS 2008 to start debugging these VB ASP.NET sites?
TIA
Crispin