Managed C++ application doesn't startup but jumps to debugger instead... Help !

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi all

I am trying to find out why a Managed C++ application which works on one machine, doesn't even startup on other machines once the executable is distributed. When the application is started on a machine other than the one is was compiled on, it doesn't start up and instead, the debugger fires up (i.e. some sort of crash occured). The .NET versions on the different computers match (both are v1.1.4322). The .NET framework is v1.0.3705. Any ideas

cheer
Luis Miguel Huapaya
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

HTTP /1.1 500 Internal Error 1
CLR error: 80004005 1
Can not run 1.0 application in .NET 1.1 4
.NET Compiler or Setup is Non-Deterministic, Solution? 5
Application crashes with error code 0xe0434f4d on exit 0
.Net 1.1 vs 2.0 5
Binding .NET application to single CPU 1
Unable to run aspnet applications 5

Back
Top