This is a strange post but i decided a long time ago i should really start collating all my knowledge in one place.
I have so many “mht” files and random txt documents with bug fixes, solutions, how to’s, best practices etc etc i should get round to putting it in one place so its easy to find.
Anyway so here is the latest bug i hjave discovered.
I was re organising our companies .NET solutions NameSpaces to align them in more of a meaning fashion. I also reorganised the folder structure of the projects so that common projects (projects used in more than one solution) are accessible from relative referencing in the various solutions.
Long story short i discovered after much work that i could not run a website in debug mode working from the locahost IIS. VS 2008 >> web >> settings >> startup options >> under the server settings select use custom server and http://localhost or whatever you have bound to the website on the local machine
This is the error i was recieving
Microsoft Visual Studio
Unable to start debugging on the web server. The debugger cannot connect to the remote computer. This may be because the remote computer does not exist or a firewall may be preventing communication to the remote computer. Please see Help for assistance.
OK Help �
Now after much research and trial and error i discovered that of the miriad of possible reasons it could be (none of the documented ones applied to me) i stumbled on the answer by experimentation. If the root folder, or any folder within the path of the website is named with the same name as the base namespace you use, this is the error you get.
so simple, just make sure you dont have a folder named after your namespace