Maximum number of warnings has been exceeded.

Maximum number of warnings has been exceeded.

• XJDM003

  Hi,

  I too have found this problem.

  Have a large client project to convert and with this limitation it is impossible for me to give

  any accurate costings for conversion

  Bob F

  
  

• nidionys

  They just released a new Web Application project for visual studio 2005 which is like the vs 2003 asp.net project. I think you will have better luck with that project type.
  
  
  

• dazza33

  The biggest issue I find with the 100 Warning limit is that the order they are generated is somewhat arbitrary (not by the type of warning).

  This tends to occure mostly when upgrading traditional ASP to ASPX and you've turned on more of the strict compiler options.
  When converting this kind of code an example where it's a productivity issue is where the old code is dominated with variant array's.

  if you correct the error " Implicit conversion from 'Object' to 'System.Array' " it will correct anywhere from 1 to 50 or more other warnings about implicit type conversion like " Implicit conversion from 'Object' to 'String' "

  So if you've sorted the warnings by description and you've corrected all the Object to Array Warnings, you now have to correct other type errors just so it will display more of the ones you should be correcting first.

  Also when a warning can be corrected with a regular expression find and replace you don't often do it becasue you may only have 1 or 2 of those types of error. But do you really, if I knew I had 10 or more of them I would use RegEx to do the fix, but I'm not going to create a RegEx for 1 or 2 errors becasue it takes longer to do then simply correcting them.

  Darren.

  
  
  

• doener

  There is the issue of how much work remains to be done, but I have another good reason to at least be able to temporarily up the number.

  I just did an upgrade of my project and of course it has 100+ warnings listed. No idea the total number. It would be nice to know how many I have left, but the bigger issue is this:What if I want to prioritize fixing the items identified by the warnings by the type of issue. I generally sort by description to lump similar issues together, but since I assume the top 100 issues are not affected by the sort order, this means I have to slog through all the warnings that I think are lower prioritiy to even see the higher priority ones.

  
  

• WillieSea

  Hi, Yudkovsky,
  
  No, the number of warnings/errors is limited to 100 (plus one to say that the maximum has been exceeded).
  
  
  
  We’ve discussed this with some customers in the past. Some don’t mind the 100-warning/error limit (under the notion that your code is mangled anyway if you have that many issues, and you might as well just slog through them), with other people (like you) rightfully wanting to know the total cost of fixing problems, without having more warnings annoyingly appear as you fix others.
  
  
  
  Heh, I was going to end this post with a request for feedback on whether folks thought it would be time well spent (given other requirements) to address this issue in what we euphemistically refer to as “a future version.” However, it’s funny – as I’m typing this, I’m wondering if that limitation is relevant anymore. That limitation was put in so long ago (near the beginning of VS2002 development, so around 7 years ago, before I switched to the compiler team) that I don’t know the rationale behind the number limitation. Probably, it was because listing out errors/warnings blocks the foreground thread, preventing you from typing while errors were listing back. However, we (well, me, ironically) fixed that issue some time ago (right before VS2002 released, if I recall correctly) so that keystrokes would short-circuit the error listing, so maybe there’s no point anymore. It could also have been a memory allocation issue, but if so I’d imagine that the limit could be set much higher.
  
  
  
  For this release, it “is what it is,” and I hope it’s not too inconvenient. However, now you’ve made me curious about this – I’ll throw this on the “things to investigate” pile and see if this could be relaxed in the future.
  
  
  
  --Matt--*
  
  

• Neal Hudson

  You can tell a lot from the vb6 Upgrade report, as it doesn't really actually compile the code.

  It won't help you with the turning strict option on, but at least its something.

  There is also the vb6 upgrade assessment tool that produces an Excel 2003 file that you can do more analysis on, such as line counts etc.
  This is what we used to get reasonable estimates for our migration.

  Hope this helps...

  Brian.

  http://www.microsoft.com/downloads/details.aspx FamilyId=10C491A2-FC67-4509-BC10-60C5C039A272&displaylang=en

  
  

• Rob Wheeler

  I've made a convertion from ASP.Net 1.1 to ASP.Net 2.0 (both vb.net) and then I had some errors and warnings (more than 100), but after fixing them all I still can't compile because I get:
  - 1 error: Maximum number of errors has been exceeded.
  - 1 warning: Maximum number of warnings has been exceeded
  
  Check this: http://www.mping.ro/ss/maxerrors.jpg
  
  

• hakkatil

  I too am going through the migration process and find this to be very frustrating. Knowing exactly how badly it is broken can assist in trying to identify that it's just tooooo broken, and rewrite these certain bits.

  (And I'd probably comment it out - or stub it) and work on the other bits...

  Having been using C++ and C# where you "see em all" I have always been happy with this...

  I hope that we can at least get a setting that we can adjust to make it bigger (or just turn it off)

  Thanks

  
  

• Ray Dyce

  100 items is fine, but sort them ALL by header click BEFORE adding to list.

  I work with warnings in the same context b.s. "Warning 106 Unused local variable: 'pr'."

  When I resolve them I can get the same "Warning 106 bla-bla-bla" lines from other sources.

  I need switch context (in brain) to other errors (warnings) with 3-8 sec time spend and 12-20 sec template solution find.

  (3+12)*1000 = 15000 sec - 4 hours out of life.

  I know that header click sort only in-grid items.

  Yes I also know that this current version 'vbc' limitation - 100 records

  Please add '/maxwarncount' command line switch for next version vbc.

  All people who need max errors will do that.

  For others /maxwarncount is the same 100 records

  Yes I can setup projects settings for warnings ignore (just now I work so), but context switched unpedictable.

  k_samsonov

  
  
• Maximum number of warnings has been exceeded.