Raise Maximum Compiler Error Limit?

**Larry Lard** · May 15 '06, 09:05 AM

Re: Raise Maximum Compiler Error Limit?

Peter Wilson wrote:[color=blue]
> 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?)[/color]

Nothing necessarily wrong with having 100 forms.
[color=blue]
>
> 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!). "SharedComponen tX 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.[/color]

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 SharedComponent X to the new project
You willl obviously get errors where SharedComponent X 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

--
Larry Lard
Replies to group please

Raise Maximum Compiler Error Limit?

Raise Maximum Compiler Error Limit?

Comment