UserControl causes app to bomb

[Scott McNair]

Hi,

I've been writing an application that relies heavily on user controls
(there are 14 in all). Today it got to a point where it was ready to
deploy, but when I try running it on any machine other than my own, it
crashes without actually launching, but posts an obscure error in the event
log:

EventType clr20r3, P1 inventory.exe, P2 1.0.0.0, P3 47acd11f, P4 inventory,
P5 1.0.0.0, P6 47acd11f, P7 e, P8 e9, P9 system.invalidoperationexception,
P10 NIL.

By commenting out huge blocks of code, I've narrowed it all down to the
user controls. They were initially declared as private, but I tried
declaring them as public with the same results.

Note, these user controls rely heavily on Infragistics controls. I've also
copied all the Infragistics DLLs (even ones I don't use) over to the remote
folder, and gave full permissions to all users for these files. It still
doesn't run.

Does anybody know why this might be behaving like this? I'll be happy to
include specific code if requested.

Regards,
Scott

 

[Armin Zingler]

Hi,

I've been writing an application that relies heavily on user
controls (there are 14 in all). Today it got to a point where it
was ready to deploy, but when I try running it on any machine other
than my own, it crashes without actually launching, but posts an
obscure error in the event log:

EventType clr20r3, P1 inventory.exe, P2 1.0.0.0, P3 47acd11f, P4
inventory, P5 1.0.0.0, P6 47acd11f, P7 e, P8 e9, P9
system.invalidoperationexception, P10 NIL.

By commenting out huge blocks of code, I've narrowed it all down to
the user controls. They were initially declared as private, but I
tried declaring them as public with the same results.

Note, these user controls rely heavily on Infragistics controls.
I've also copied all the Infragistics DLLs (even ones I don't use)
over to the remote folder, and gave full permissions to all users
for these files. It still doesn't run.

Does anybody know why this might be behaving like this? I'll be
happy to include specific code if requested.

I'd put the code in Sub Main into a Try-Catch block and log/show
exception information, in particular the stack trace. If you also deploy
the *.pdb file and compile the Debug config, you'll also get the line
number where the error occurs.


Armin

 

[Scott McNair]

I'd put the code in Sub Main into a Try-Catch block and log/show
exception information, in particular the stack trace. If you also deploy
the *.pdb file and compile the Debug config, you'll also get the line
number where the error occurs.

I found the problem... it was due to a separator line that I'd put in the
app early in development, which required the PowerPack dll's. I didn't
actually need the separator, so I removed it and it ran fine.