Start w/o debugging means that the code will ingore any hooks you place in code so, if you have a section of problematic code and want to see whats going on in it, you will not be able to step into it.
I have had this problem before, but, only when working with a remote server. The one time I had this problem with my machine, it had to do with the fact that I had 2 versions of .NET installed in IIS 1.1 and 2.0.
The directory that had my application (designed in 1.1) was configured to execute with the 2.0 framework and Visual Studio couldn't start debugging on my project because of this. I configured the directory to run under 1.1 and everything worked fine.
Visual Studio should give you links to the MSDN when you get that error, read EVERYTHING on that page because there are multiple reasons why this would fail.
================================================== =========
Read this if you want to know how to get a correct reply for your question:
http://www.catb.org/~esr/faqs/smart-questions.html
^^Took that from planoie's profile^^
^^Modified text taken from gbianchi profile^^
================================================== =========
Technical Editor for:
Professional Search Engine Optimization with ASP.NET
http://www.wiley.com/WileyCDA/WileyT...470131470.html
================================================== =========
Why can't Programmers, program??
http://www.codinghorror.com/blog/archives/000781.html
================================================== =========