I'm having a problem with an ASP.NET website created in Visual Studio
2005 (using C#) where the debugger can identify that there are errors
preventing it from compiling but it won't show the filename or the line
number that generated the error. I'm going bananas trying to figure it
out. I've tried closing and reopening VS, doing a full rebuild instead
of just pressing F5, and there I ran out of ideas.

Is there an option somewhere that may have somehow activated itself
that says I'm not really interested in knowing the location of these
errors? I can't double-click on the errors to go to the location,
either... I'm stuck with errors but way of finding them :-(

I found the problem (after much searching, even with non-Google search
engines I was *that* desperate for more results): it turns out that
there is some really helpful bug in Visual Studio 2005 whereby you
don't get file names or line numbers in the Error List if your solution
lives in a directory with parentheses in the path. Here's the article I
found:

http://www.dotnetmonster.com/Uwe/Forum.aspx/vs-net-ide/4006/Error-List-Missing-the-Code-File-Reference

Put this together with the really nasty bug in the compiled HTML help
file engine under Windows whereby it loads the index but not the
content if the file has a hash ("#") in the name, Microsoft bugs have
really, really, eaten up a lot of my time... Now, if only Linux wasn't
a festy gutter of collected bits and pieces of rubbish that can't even
agree on a way to exchange clipboard data, I might just think about
switching....

[quoted text, click to view]