Visual Studio - problem opening web application with mixed authentication on subfolders - by A. Tarasul

Status : 

  Postponed<br /><br />
		Due to current priorities, the product team decided to postpone the resolution of this item.<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 377142 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 10/22/2008 12:05:56 PM
Access Restriction Public


0. Create 2 level folder structure on disk with html file in subfolder.
1. Created web application on Vista localhost
2. Set application authentication to windows only
3. Set authentication to subfolder to anonymous only.
4. Open web application in visual studio (running as local administrator)
5. The subfolder shows up in solution explorer with green dot, but it pointed to root of web application, not to subfolder as it should.
6. However if subfolder was converted to virtual directory - everything works as expected.
Sign in to post a comment.
Posted by Microsoft on 12/22/2008 at 11:58 AM
Thanks for your feedback. This is a known issue with IIS right now. The IIS team is considering possible resolutions. If you are interested in possibly participating in the verification of a fix for this issue, please email me at johndund at microsoft dot com and I can possibly set you up with a private and look to get your problem resolved.

- The Visual Web Developer Team
Posted by Microsoft on 11/10/2008 at 4:37 AM
Thanks for your feedback. We are escalating this bug to the product unit who works on that specific feature area. The team will review this issue and make a decision on whether they will fix it or not for the next release.

Thank you,
Visual Studio Product Team
Posted by Microsoft on 10/28/2008 at 3:30 AM
Thank you for your feedback, We are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(

If at any time your issue is closed unsatisfactorily, you may edit your issue via Connect and change the status to “Active.”

Thank you,
Visual Studio Product Team