We have a solution in which there are several different web applications: the solution has different TFS branches. Web applications are configured to use IIS on the local machine.
When you open another branch of the solution, you get the message:
The local IIS Url http: // localhost / AppName specified for the AppName web project has not been configured. To open this project, you must configure a virtual directory. Do you want to create a virtual directory now? Well no.
If you click Yes, you will receive a second error message:
Creating the virtual directory http: // localhost / AppName failed: the URL http: // localhost / AppName is already mapped to a different folder location.
This is obviously correct, because it maps to another branch. This used to work fine, and Visual Studio automatically reassigned the folder for me, but after reinstalling Visual Studio it no longer works, and I get a second error message. Another of my colleagues has no problems with this, and he automatically redirects the folder for him after hitting yes on the first message. I am running Visual Studio 2010 as an administrator and can create virtual directories (if they do not already exist) from the Project Properties page.
- -, , . , - , .