Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m using native pinvoke calls in my app and external assemblies in dlls.
Everything is working fine, until part of the program stops working and I get:
“A first chance exception of type ‘System.Runtime.Remoting.RemotingException’ occurred in mscorlib.dll”
multiple times in the Debug Output Window. The execution continues, it just prints that in the output window when I try to execute my code. How to get where the exception occurred?
Keep in mind the difference between first-chance and second-chance exceptions. A first-chance exception is throw but may be being caught and handled before you even see it. This is normal and not too much of a cause for concern.
A second-chance exception is when the exception is throw, and no one catches it, so the exception becomes unhandled and may cause your program to terminate.
Are you concerned just on the debug text, or is it not working? If it works I wouldn’t worry. If it’s a big concern catch it in WinDebug and analyze it, or you can tell the visual studio IDE to stop on first-chance exceptions.