views:

34

answers:

2

I'm cleaning up a project to get rid of all the warnings, but I can only see the first 100 or so in the Error List pane.

This is a problem because we're using Team Server for source control and all the warnings shown are in files that are currently checked out (and therefore I can't modify without making someone else possibly do a lot of work when they check in).

I'd like to be able to see the full list so I can continue my cleaning while others are working.


In case it makes a difference,

  • The project in question is a VB.NET web application (using the application model). It doesn't seem that I can compile individual pages.
  • Environment is VS2010 Premium; I can get Ultimate on my machine if necessary.
+1  A: 

The full list of warnings should be visible in the output window. After building open the output window, switch it to the build output and you should have access to all errors emitted by the compiler.

Note: The compiler itself still has a hard limit on the number of errors it will report for a given project (true for both VB and C#). This cannot be overridden in Visual Studio or the command line.

JaredPar
The Output pane says "vbc : warning BC42206: Maximum number of warnings has been exceeded." and shows the same as the Error list. Regardless, if the compiler has a hard limit at ~100, then I guess I'm kinda stuck?
Jon Seigel
@Jon, unfortunately yes. This number is hard coded into the compiler and cannot be overridden by even hacky means.
JaredPar
+1  A: 

Can't you temporarily locally do something similar to

#pragma warning disable 

in the files which are checked out by the others so you don't have to see their warnings?

Andreas Brinck
Hmmmm... I suppose I could. On check-in, I'd have to go back and figure out which files are the ones I *shouldn't* check in. This doesn't really answer my original question, but +1 because it's helpful. Thanks.
Jon Seigel

related questions