I like the semantic error underlining, I do, but I've been finding it annoying trying to sort out the build errors from the semantic errors. I can run a build, see the errors getting generated, but as soon as I go to try clicking on the build errors, the
Error List starts getting populated with semantic errors again, losing the build errors in the crowd, and in some cases with ASP.NET pages, the build errors actually get
lost; the error list seems to get cleared halfway through error generation.
The only way to truly avoid it is to close most or all of the open files in the editor.
What I would like to know is if there is a possible means to separate out the build and semantic errors so that they do not share the same Error List. If not in the IDE itself, might there be some means of creating an IDE extension to do the same?
Alternatively, is there a way to close all open files such that they can be re-opened en masse, somewhat like a "bookmark all tabs"?
Ritchie Anna...
Member
2 Points
2 Posts
Build Error and Semantic Error Interference
Apr 09, 2009 06:13 PM|LINK
I like the semantic error underlining, I do, but I've been finding it annoying trying to sort out the build errors from the semantic errors. I can run a build, see the errors getting generated, but as soon as I go to try clicking on the build errors, the Error List starts getting populated with semantic errors again, losing the build errors in the crowd, and in some cases with ASP.NET pages, the build errors actually get lost; the error list seems to get cleared halfway through error generation.
The only way to truly avoid it is to close most or all of the open files in the editor.
What I would like to know is if there is a possible means to separate out the build and semantic errors so that they do not share the same Error List. If not in the IDE itself, might there be some means of creating an IDE extension to do the same?
Alternatively, is there a way to close all open files such that they can be re-opened en masse, somewhat like a "bookmark all tabs"?
Regards,
-- Ritchie Annand
Visual Studio 2008 error messages "code editor"