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)?
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