When i run an application an exception is caught how to handle this?

Question

4.13/5 (5 votes)

See more:

When I run an application using Quick test professional an exception is occurred as System.ExecutionEngine exception.

How to handle this?

Initialised an object of a Windows Form as form1

if (form1.ShowDialog(IWin32Window owner) == DialogResult.OK)

at this line exception occurs.

How to handle this?

Reply

Posted 6-Mar-11 22:54pm

yeshgowda

Updated 7-Mar-11 20:20pm

Hans Dietrich

v6

Add a Solution

Comments

johannesnestler 7-Mar-11 6:01am

1. You exception is not "caught"! - Wrap your code in a try-catck block as Ryan Zahra showed you.
2. If you can't solve it - post the complete exception message (ex.ToString()) here
3. The example you showed is wrong: In the line "ptsd.ShowDialog(IWin32Window owner)" you have to give a instance of a IWin32Window to the ShowDialog method. This code can not compile...
-> So show your real code (or a real example), show your complete exception message, do so everytime you want help with an exception. Best Regards

johannesnestler 7-Mar-11 8:11am

Ok, thank you for showing the code - now I understand your problem better. But I can not give you a hint what's wrong - sorry, code looks good to me. Did you look up the exception help on msdn? http://msdn.microsoft.com/en-us/library/system.executionengineexception(v=vs.80).aspx

-> Sounds bad. Did the message show an additional error code? I would try the code on another machine, maybe the runtime system is corrupted.

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Ryan Zahra · Accepted Answer · 2011-03-06T22:59:00

Solution 1

You should wrap your code in a try catch block

try
{
     ISchemaEditor ptsd = new ProductionTableSchemaDesigner();
     if (ptsd.ShowDialog(IWin32Window owner) == DialogResult.OK)
     {
     }
}
catch(Exception ex)
{
     //log your exception
}

Posted 6-Mar-11 22:59pm

Ryan Zahra

Comments

yeshgowda 7-Mar-11 8:00am

Exception is not caught in catch block.

Sergey Alexandrovich Kryukov 7-Mar-11 13:08pm

I explain what to do in this case in my Answer, please see.
--SA

Sergey Alexandrovich Kryukov 7-Mar-11 13:09pm

This is correct, my 5, but OP did not observe exception, so I added the advice in my Answer.
--SA

Espen Harlinn 6-Apr-11 16:04pm

NIce and simple answer, my 5

Sergey Alexandrovich Kryukov · Accepted Answer · 2011-03-07T07:08:00

Answering follow-up Question in response to the Answer by Ryan:

Exception is not ~~catched~~ caught in catch block.

It simply means one of the two: 1) you report is incorrect; exception is thrown elsewhere, 2) exception is caught but you failed to detect it because wrong exception handler, for example; simply use debugger.

Assuming you would not miss caught exception (case 2); but exception is thrown elsewhere, here what to do:

Catch exception at the very top of the stack of for each thread. Make sure you never block exception from propagation anywhere in the middle; if you catch any exception, always re-throw it in the same block or throw another exception (except the very top where you show exception somehow, never hide it completely). There are very few exclusions from this rule, usually as a last resort in case of some ill-designed 3-rd party libraries.

To get full exception information and locate to source of it, make full exception dump in your top-level exception handler: include exception Stack (most important) and collect exception information on all inner exceptions, recursively (use Exception.InnerException). You can save dump in some file or System.Diagnostics.EventLog. By the way, this is the information you may need to use in your CodeProject Questions.

For System.Windows.Forms.Application, "very top" is in the main UI cycle.
This is how: add a handler to Application.OnThreadException (show exception info in UI); to make this event firing, assign Application.SetUnhandledExceptionMode to UnhandledExceptionMode.CatchException.
Attention! It won't happen by default!

For WPF, there is a similar technique. You need to handle the event Application.DispatcherUnhandledException.

[EDIT]
Additionally or alternatively, handle the events System.AppDomain.UnhandledException and System.AppDomain.FirstChanceException.
Credit to Espen Harlinn for the idea.

See also: How do i make a loop that will stop when a scrollbar reaches the bottom[^]
[END EDIT]

—SA