S
Samuel R. Neff
Occasionally we get this error message when running an app on a test
machine:
[name].exe - Common Language Runtime Debugging Services
Application has generated an exception that could not be handled.
Porcess id=[id], Thread id=[id].
Click OK to terminate the application.
Click CANCEL to debug the application.
Under what conditions does .NET use this useless message instead of
the normal one that says the error and stack trace and such? Is there
any way to turn off the debug option, since this is on a machine that
can't do debugging anyways?
This seems to happen when there's an error before our application
initializes, like with a missing DLL or problem in the constructor for
certain objects used within Main.
Thanks,
Sam
B-Line is now hiring one Washington D.C. area VB.NET
developer for WinForms + WebServices position.
Seaking mid to senior level developer. For
information or to apply e-mail resume to
sam_blinex_com.
machine:
[name].exe - Common Language Runtime Debugging Services
Application has generated an exception that could not be handled.
Porcess id=[id], Thread id=[id].
Click OK to terminate the application.
Click CANCEL to debug the application.
Under what conditions does .NET use this useless message instead of
the normal one that says the error and stack trace and such? Is there
any way to turn off the debug option, since this is on a machine that
can't do debugging anyways?
This seems to happen when there's an error before our application
initializes, like with a missing DLL or problem in the constructor for
certain objects used within Main.
Thanks,
Sam
B-Line is now hiring one Washington D.C. area VB.NET
developer for WinForms + WebServices position.
Seaking mid to senior level developer. For
information or to apply e-mail resume to
sam_blinex_com.