Progrma crashing on other PCs

  • Thread starter Thread starter gerryR
  • Start date Start date
G

gerryR

Hi All

I've written a small app, I'm running VS2008 Standard and if I look at the
advanced compile properties I see the target Framework is 3.5.

The app runs fine on my Laptop but I've tried it on 4 other PCs in work and
it instantly crashes with the standard "send error report" message. All PCs
including my laptop are running XP SP2 or SP3. At least one of the other
PCs I tested had the .net Framework 3.5 installed and it still crashed.

Is there any way to see whats causing the crash? Could the fact that my
laptop has .net 3.5 SP1 installed but the other one doesn't have SP1 be the
cause?

Thanks for any help
Gerry
 
Is there any way to see whats causing the crash? Could the fact that my
laptop has .net 3.5 SP1 installed but the other one doesn't have SP1 be
the cause?
Click to expand...

I would say that is your problem.


__________ Information from ESET NOD32 Antivirus, version of virus signature database 4240 (20090713) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com
 
Hi All

I've written a small app, I'm running VS2008 Standard and if I look at the
advanced compile properties I see the target Framework is 3.5.

The app runs fine on my Laptop but I've tried it on 4 other PCs in work and
it instantly crashes with the standard "send error report" message.  All PCs
including my laptop are running XP SP2 or SP3.  At least one of the other
PCs I tested had the .net Framework 3.5 installed and it still crashed.

Is there any way to see whats causing the crash?  Could the fact that my
laptop has .net 3.5 SP1 installed but the other one doesn't have SP1 be the
cause?

Thanks for any help
Gerry
Click to expand...

If you have an ActiveX COM component, don't forget to register it on
target machines using regsvr32 or provide a manifest file to make them
registration-free.

Beside this, there may be a timing problem related to computer's
performances and length of task based on what your application does at
startup (form_load or sub main).

Onur Guzel
 
Hi All

I've written a small app, I'm running VS2008 Standard and if I look at the
advanced compile properties I see the target Framework is 3.5.

The app runs fine on my Laptop but I've tried it on 4 other PCs in work and
it instantly crashes with the standard "send error report" message. All PCs
including my laptop are running XP SP2 or SP3. At least one of the other
PCs I tested had the .net Framework 3.5 installed and it still crashed.

Is there any way to see whats causing the crash? Could the fact that my
laptop has .net 3.5 SP1 installed but the other one doesn't have SP1 be the
cause?

Thanks for any help
Gerry
Click to expand...

You need to handle exceptions in your app to determine what the
exceptions are. Also, are you actually installing the app on the
other PCs or are you trying to run it from a network share?

You need to get the exception and its stack trace to determine what
your problem is.

Chris
 
Running from the network share was the problem all right, machines with the
3.5 framework run it fine when I copy it to the desktop.

Thanks for that!

gR
 
Strange thing is, it runs on the PCs without 3.5 on them too. Even though
when I changed the target framework to 2.0 is kicked up a load of errors and
wouldn't compile.

Thanks again
gR
 
gerryR said:
Strange thing is, it runs on the PCs without 3.5 on them too. Even
though when I changed the target framework to 2.0 is kicked up a load
of errors and wouldn't compile.
Click to expand...

ICBW, but ISTR 3.5 made the security more restrictive and 3.5SP1 relaxed it
to include running from network drives.

If you prog doesn't use any 3.5 features, then it is only using 2.0
features, which is why it ran.

You might have to remove any references to 3.5 dlls after changing the
target framework to 2.0 to compile it.

Andrew
 
Thanks for the information Andrew, I'll look at removing any links to 3.5

Just glad it's working without needing 3.5, it's really not worth that
install :)

Thanks again,
Gerry
 
Back
Top