Coffeehouse Thread

6 posts

Max errors in Visual Studio - alternatives

Back to Forum: Coffeehouse
  • davewill

    Maximum number of errors has been exceeded.  We've all seen it (I'd presume) and we know why.  Additionally we sympathise with the visual studio team as to how hard it is to balance performance in this situation.

    So it is what it is.

    I'm in a situation where I'm doing a major rework of a solution and I've been working through the code changes in compiler generated order for about 3 weeks now.  It is hard on the brain knowing that significant progress is being made but having nothing tangible to gauge it by is _________.  I'm not sure what the right descriptive word would be.  "Disheartening" conveys the slumped shoulders ho hum keep going but carries with it a negative conotation, which isn't the case.

    I haven't heard of a setting that will increase the maximum error limit.  You know, one of those nobody should ever know about this reg entry and it is a use one off, one time, at your own risk type of thing.

    Just being able to occasionally see the full error list so as to keep some weekly sanity would be nice.  Anyone want to share their secret or alternative for sanity in such a situation?

  • kettch

    @davewill: Is there any way you can break it up into smaller projects? Or is it not componentized like that?

  • davewill

    @kettch: Unfortunately no.  Part of the rework involves a lot of reorg as well.  The reorg is in the reverse direction.  The solution projects were too granular and now the overall solution is being simplified, name spacing reworked, and made into saas.

  • davewill

    Woot!  Friday + finally no compile errors = great weekend

  • warren

    The amount of time required to product a complete error/warning list for a large, broken C# solution is probably more than you'd like to spend waiting on a compile.  The number isn't going to be accurate as the number of errors increase anyways, since you can easily end up in situations where hundreds of errors are caused by a single off-by-one typo; conversely, a single typo (say, an unclosed multi-line comment for a simple example) could hide many errors.  Attempting to measure how long a solution will take to fix using this number is therefore useless.

    But there is still a way to see what kind of mountain you have to climb -- use Resharper. Its Errors in Solution" window can be of some help with getting past the compiler limit. 

    In general, Resharper is a very good tool when doing some brownfield recovery.  The number of warnings you'll see in the Code Issues window will probably require a trip to a therapist, since it not only covers compiler warnings, but hundreds of different potential problems (redundant casting, parentheses, forgetting to specify culture in string.IndexOf(), forgetting semicolons at the end of Javascript statements**, etc.) but you can sort the problems by type and fix them across your solution all at once.

    Resharper isn't the only game on the block, either -- JustCode and CodeRush are both very good tools as well and are priced similarly to Resharper.

     

    (** yes I know it's not strictly necessary for the code to run but some JS minifiers don't handle missing semicolons very well)

  • davewill

    @warren: Thanks for sharing your insight.

Comments closed

Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums, or Contact Us and let us know.