I am running a VB.Net conversion project and have run into a severe
problem compiling the application. The project has a main project with
about one hundreds forms. (Did I say badly structured?)

The number of compiler errors is limited to 100 approx. These errors
from various forms all relate to a missing shared component which
references everything else in sight (VB6 rules!). "SharedComponentX is
not a member of NamespaceY"

I never reach any of the errors for the shared component so I have no
way of fixing it. I am reduced to trying to compile the shared component
without any help from the VB compiler (Ugh!)

Surely this is a bug in the VB compiler? It should present errors in a
bottom up way, instead of top down.

Is there any way to increase the compiler limit?

Peter Wilson wrote:
Nothing necessarily wrong with having 100 forms.

I would think working out the top and the bottom would be beyond a mere
compiler :)

Perhaps you could try this:

Create a new blank project
Add SharedComponentX to the new project
You willl obviously get errors where SharedComponentX refers *out* -
but hopefully you will also get the internal problems, which you can
then fix
Now from the main project, you will be able to fix the 'top' errors now
that the 'bottom' ones are fixed

Storing collection of one class inside another
to read a textfile regarding his format
Session variable as string (array)
code convertor in VB.NET Express Edition
using MDIList in a MDI form
Access MDI child properties generically
Need one Regular Expression
word automation bookmarks
vb.net 2005 bug in the ide (wipes out code)
Hide an application to taskbar by the clock