App bombs in production

[John]

Hi

I have a vs 2003 win form app which runs fine in IDE but once it is deployed
via setup it bombs on start-up screen and wants to send MS the error report.
This happens on multiple pc including the development machine so problem is
probably not with pcs.

What is the problem and how can I fix it?

Thanks

Regards

 

[Guest]

What is the problem and how can I fix it?

You'll have to attach a debugger.

If it's crashing on the constructor, that'll be harder to debug. But it can
be a variety of issues such as missing certificates, missing ActiveX
controls, etc.

 

[John]

How do I attach the debugger? Sorry for being dumb.

Thanks

Regards

 

[Andrew Stewart]

John, Have you just added an icon to your application? vb applications have
an issue with 256x256 WinXP icons. Found this out the hardway.

 

[Phill W.]

I have a vs 2003 win form app which runs fine in IDE but once it is deployed
via setup it bombs on start-up screen and wants to send MS the error report.
This happens on multiple pc including the development machine so problem is
probably not with pcs.

Some Possibilities:

(1) Security.
Is the code /all/ installed locally, or is any of it being loaded and
run from network file shares? If the latter, then they will be
"sandboxed" and run with a reduced set of privileges.
Also, if you have Fx1.1 and Fx2.0 on the target machine, you may find
that it's being loaded into the /more recent/ run-time - any security
settings that you put in place for Fx1.1 will have to be duplicated for
Fx2.0.

(2) Just checking: The Framework /is/ installed on [all] the target
machines, isn't it?

(3) When you say "bombs" - what do you get from the StackTrace of the
Exception that's been thrown? Have a look in the Windows Event Viewer;
if you're lucky, you may find some evidence of the exception logged in
there.
Of course, you /should/ be catching the Exception /before/ it wriggles
its way "out" of your program, but that's another story...

HTH,
Phill W.

 

[Miha Markic]

Perhaps you are missing a 3rd party assembly on target machine.

 

[rowe_newsgroups]

Hi

I have a vs 2003 win form app which runs fine in IDE but once it is deployed
via setup it bombs on start-up screen and wants to send MS the error report.
This happens on multiple pc including the development machine so problem is
probably not with pcs.

What is the problem and how can I fix it?

Thanks

Regards

Do you get any error messages besides the one that wants to report the
error to Microsoft? Generally speaking, most apps that bomb also give
an error box that will display some sort of helpful message and often
a generic stack trace. One thing to check is if other .NET 1.1 apps
work on that machine when deployed in a similar environment?

Also, what does this question have to do with the ADO.NET group?

Thanks,

Seth Rowe [MVP]

 

[kimiraikkonen]

Hi

I have a vs 2003 win form app which runs fine in IDE but once it is deployed
via setup it bombs on start-up screen and wants to send MS the error report.
This happens on multiple pc including the development machine so problem is
probably not with pcs.

What is the problem and how can I fix it?

Thanks

Regards

First, you need to determine "when" your application bombs. For
example if your application bombs just when you launch it, put try-
catch exception handling block to in your form1_load (mybase.load)
event. This really helps to guess the reason of your problem, tested.

If you still no luck to guess, make sure where you missed these try-
catch blocks in your source code.

Hope you solve.