Visual Studio has a nice feature where it can automatically reconfigure IIS for you when you run a suitable “services” project.

The benefit is that you don’t need to manually mess with IIS - just a one time check to make sure the virtual directory set in your .csproj is correct and everything will “just work” reguardless of the folder in which you check out your source code.

The downside is the effect when you have two copies of your source checked out for different purposes - unless you disable this feature, you’ll keep finding the same server handling both of your configured virtual directories, instead of each server remaining separate.

As usual, oddball behaviour when debugging has a relatively simple cause - the challenge is in finding that simple explanation when you see some really weird symptoms.


blog comments powered by Disqus
Next Post
Simpler code with DirectoryInfo  13 May 2014
Prior Post
WordTutor release 1.0.2411  11 Feb 2014
Related Posts
Using Constructors  27 Feb 2023
An Inconvenient API  18 Feb 2023
Method Archetypes  11 Sep 2022
A bash puzzle, solved  02 Jul 2022
A bash puzzle  25 Jun 2022
Improve your troubleshooting by aggregating errors  11 Jun 2022
Improve your troubleshooting by wrapping errors  28 May 2022
Keep your promises  14 May 2022
When are you done?  18 Apr 2022
Fixing GitHub Authentication  28 Nov 2021
March 2014