I started to think that it is just you and me getting these kind of errors and there is a curse all around us!
It is like "Internet Explorer cannot open the web page" error I have seen today, though Firefox can open it pretty fine.
I got the same error message these days on a fresh installation of Visual Studio and a project that loads happily on other machines. It was kind of stupid mistake to forget to install IIS (as the project used it)...
It would be a great solution if the environment asks to change that URL instead of try-catch'ing the COMException.
Many thanks! - My issue was exactly as you stated - wrong IISUrl. Updated the reported bug to account for this scenario.
Thanks much!
Today I come to the same problem and in my mind came that I have seen this in your blog!
Thanks man. I just was prepared 
.
Thanks for the pointer! This really helps. One question, how did you go about debugging this problem through windbg? I tried with cdb but the exception didn't crash into the debugger. Thanks!
Hi Eddie,
this was quite a while and I do not really remember details. But in order to get cdb or windbg stopping on all exceptions you must run sxe command first to enable first chance exception handling. Most probably it will stop when it tries to load the URL and that's how I probably guessed that my IIS site was not set up.
Basically it should not make any difference if you are using cdb or windbg at all.
Thanks for this info, it helped me sort it out, I'll post our scenario in case it helps others.
This occurred for us on our W2k3 build server.
Because this was just a build server, we have no need/desire for IIS to be installed.
In the Web properties page for the project, Uncheck the box that says 'Apply server settings to all users (store in project file)'. This will then remove the dependency on IIS for vanilla builds, but dev users can change their IIS location on a per-machine basis (which is probably correct for development anyway).
Hope this helps.
Carl
Thanks for the tip, Carl!
Commenting by HaloScan
