Special thanks to John Dundon at Microsoft for helping solve this problem. Here is what he said:
Thanks for all the details. This actually looks like fancy behavior in VS, I think I can help you work around.
I believe that the reason for remembering it is to use the local development server because it is stored in the SUO file. Thus, there are two possible ways to fix this:
- Re-open the solution from the source control as an administrator on machines with IIS installed and everything should be loaded in its correct place
- If you close VS, delete the SUO file (note - this will erase some state settings of your solution, but there should be no data loss), and then reopen the solution, it should ask you to reload this particular website and try to make it IIS website again.
Please note, however, since the virtual directory already exists in your machine, and it will ask you if you want to use it - I assume that you do, but it will overwrite any files when it does.
Let me know if this works for you (and so far you donβt technically need to, it might be a good idea to back up any work done on it that has not been verified before trying it).
I followed his advice and deleted my SUO file and reopened the solution. The website was automatically committed as http: // localhost / Website , and it also checked the .SLN file, and when I checked it, it fixed the release for other developers. Hope this solution helps others as well as with this unusual problem.
Noah
source share