G
Guest
I wrote a WindowsForms application and I compiled, installed, and run it on
my computer without any problems. When I install it on another computer that
doesn't have VS.NET installed I get the following error message immediately
after I double-click on its icon:
"MyApp.exe - Common Language Runtime Debugging Services
Application has generated an exception that could not be handled.
Proess id=0x884(2180), Thread id=0xb14(2386).
Click Ok to terminate the application.
Click CANCEL to debug the application.
"
The dot Net Framework is installed on all my computers and I have other
applications that I wrote before working fine on this computer. The problem
is I don't know where to look for the cause of this problem and since I don't
have a "Registered JIT debugger" on the machine in question I can't
troubleshoot it there.
I tried to add in the "Form_Load" event something like: 'Msgbox ("Test")' to
see if my application reaches the Form_Load stage before it generates the
error. And it never showed that message box. So I'm assuming the exception
occurs even before that!
Does any one know how we can troubleshoot/debug in this situation?
my computer without any problems. When I install it on another computer that
doesn't have VS.NET installed I get the following error message immediately
after I double-click on its icon:
"MyApp.exe - Common Language Runtime Debugging Services
Application has generated an exception that could not be handled.
Proess id=0x884(2180), Thread id=0xb14(2386).
Click Ok to terminate the application.
Click CANCEL to debug the application.
"
The dot Net Framework is installed on all my computers and I have other
applications that I wrote before working fine on this computer. The problem
is I don't know where to look for the cause of this problem and since I don't
have a "Registered JIT debugger" on the machine in question I can't
troubleshoot it there.
I tried to add in the "Form_Load" event something like: 'Msgbox ("Test")' to
see if my application reaches the Form_Load stage before it generates the
error. And it never showed that message box. So I'm assuming the exception
occurs even before that!
Does any one know how we can troubleshoot/debug in this situation?