IIS Debugging VS 2008 With Vista Home Premium - by smaclell

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 387883 Comments
Status Closed Workarounds
Type Bug Repros 2
Opened 12/12/2008 12:22:50 PM
Access Restriction Public


I am attempting to debug a website through IIS using VS. This is partially an issue due to my version of Vista (Home Premium) and VS. After crawling through forums I found that it was because this version of Vista cannot install the IIS component for Windows Authentication. For VS 2005 a hot fix was released that allows this scenario to work (http://support.microsoft.com/kb/937523).

This issue is blocking me from testing Azure based services on my PC. It appears to require this Windows/VS feature. I could not find anywhere in Microsoft Connect to create Azure related bugs/feature requests so if you could also forward me there that would be great.
Sign in to post a comment.
Posted by mastak.ua on 6/11/2009 at 10:41 AM
Verified on Vista Business SP1. Same issue.

Gregg Miskelly suggestion:
"1. Open 'Internet Information Services (IIS) Manager'
2. Expand the 'Sites' node
3. Remove any stale sites that have configuration which is no longer valid.

Does this resolve the issue?"

Posted by Microsoft on 4/27/2009 at 3:58 PM

I am resolving this as 'fixed' because we believe the issue will be fixed with Visual Studio 2010.

If anyone encounters this issue with VS 2008, try the work around from below. This error occurs while querying the IIS object model to determine which process to debug, which is a code path that the debugger will only take if Windows Authentication is disabled/not installed/broken.

Gregg Miskelly
Posted by smaclell on 4/21/2009 at 11:43 AM
Sorry I am unable to test your suggested resolution as I have reconfigured my computer. Previously I was using Windows Vista Home Premium and have since then upgraded to the Windows 7 Beta. I believe that the issue was caused by not being able to install the "Windows Authentication" option under Vista Home Premium. Since the configuration is different I don't believe it would reproduce the bug.
Posted by smaclell on 4/21/2009 at 11:25 AM
That was part of my problem. Since I was using Windows Vista home premium I could not install the option needed to enable windows authentication.
Posted by Microsoft on 4/20/2009 at 3:00 PM
Thanks for reporting this issue. We have seen this same problem in the past on computers with bogus information in the IIS configuration store.

Can you try the following?

1. Open 'Internet Information Services (IIS) Manager'
2. Expand the 'Sites' node
3. Remove any stale sites that have configuration which is no longer valid.

Does this resolve the issue?
If so, did you need to remove sites created by the Windows Azure Tools for Visual Studio?

Thank you,
Gregg Miskelly
Visual Studio Debugger Developer
Posted by BillHie on 4/17/2009 at 2:40 PM
Can you try enabling windows authentication on your IIS web server? See http://blogs.iis.net/brian-murphy-booth/archive/2008/06/03/visual-studio-2008-unable-to-debug-asp-net-app-on-iis-7-0.aspx
Posted by Microsoft on 12/17/2008 at 2:16 PM
Thanks for your feedback, your bug has reached the Windows Azure Tools for VS team. We're investigating the problem and will keep you updated on the progress.
Posted by Microsoft on 12/14/2008 at 11:32 PM
Thanks for your feedback.

We are escalating this issue to the Cloud Computing group within the Visual Studio Product Team for triage and resolution.
These specialized experts will follow-up with your issue.

Thank you,
Visual Studio Product Team