Question

VB.NET has this rather annoying limitation which caps compiler warnings reported at 100.

vbc : warning BC42206: Maximum number of warnings has been exceeded.

This makes things rather frustrating when trying to size up the amount of effort that would be required to comply with VB.NET best practices, such as enabling Option Strict.

Is there any way where this limitation could either be removed, adjusted, or could warnings be gathered by some other means (such as through a 3rd party code-analysis tool)?

Answer 1

As of VB11, in VS2012, vbc no longer has a maximum error limit when called from the command line.

There s probably a better link for this now, but this will do until I find one.

UPDATE: new link

Answer 2

The official answer is apparently "No." From Microsoft: "While this issue does exist, the Visual Basic Compiler Team has decided to leave the hard limit to the reported errors because it helps with performance."

Answer 3

You should read Configuring Warnings in Visual Basic and How to: Enable or Disable Compiler Warnings

For example, you can to the compiler options (under the project build properties) the following line

warnaserror:42206

this should (I haven t tried it myself...) disable your 100 errors limit.

On another note, 100 warnings is a very large number. You should probably go over your code, check and fix the reasons to those warnings.

Answer 4

I ve had the same problem with SQL projects I ve been working on; the limit is 200 warnings. Then as I fix them, new ones merge in so the number never goes down!

I found that if you look in the "Build" output in the "Output" tab you can see everything. In my case I have thousands. Just select all and copy/paste it into a text editor.

友情链接