what are the best practices for using a try catch block

Question

0.00/5 (No votes)

See more:

Hello...What are best practices for using try catch blocks,In my project i am using try catch block for Sql Executions and Calculations parts only..is it ok???
Pls Help

Posted 23-Feb-11 18:37pm

Yatin Bhagat

Add a Solution

Comments

Obaid Ahmed 24-Feb-11 1:27am

Exception Handling has to be present every where in code, where code will possible to crash in any worst situation.

Sergey Alexandrovich Kryukov 24-Feb-11 1:59am

Not accurate, wrong in many cases. Structural Exception handling is designed to minimize and isolate error processing.
--SA

Obaid Ahmed 24-Feb-11 2:07am

ya ya.. I'm not talking about Structural Exception Handling, yes you are rite!

Sergey Alexandrovich Kryukov 24-Feb-11 3:25am

All other error handling techniques are rendered obsolete with inventions of structural exception handling by Barbara Liskov and by implementation of this technology on all platforms.
--SA

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)

Nish Nishant · Accepted Answer · 2011-02-23T18:40:00

Solution 1

Relevant article on MSDN:
http://msdn.microsoft.com/en-us/library/seyhszts.aspx[^]

Popular article on this topic here on CodeProject:
Exception Handling Best Practices in .NET[^]

Posted 23-Feb-11 18:40pm

Nish Nishant

Comments

Sergey Alexandrovich Kryukov 24-Feb-11 1:28am

Good, my 5.
From all developer's mistakes about exceptions one is a champion in creating disaster; I dedicated my answer to this topic, please see.
--SA

Nuri Ismail 24-Feb-11 3:18am

Very useful links! 5+

Espen Harlinn 24-Feb-11 4:06am

Good links :)

Sergey Alexandrovich Kryukov · Accepted Answer · 2011-02-23T19:27:00

Solution 2

Most frequent and disrupting mistake is in the catch block: many developer catch exception and blocking its further propagation up the stack. Such blocking should be done only on very top of each stack, to prevent termination of application, also in the main cycle of event-oriented UI (such as inside Application.Run, the libraries provide special events and options to handle thread exceptions on this level). In almost all other processing exception should be re-thrown again throw throw, optionally, low-level exception can be caught, and semantic-aware exception thrown (the caught exception should be placed in InnerException of the newly created exception).

Exclusions from these recommendations are relatively rare; usually, blocking of all or some exception from propagation up the stack is used as a work-around of some defects in the some code, when its source code in not available for fixes.

—SA

Posted 23-Feb-11 19:27pm

Sergey Alexandrovich Kryukov

Comments

Abhinav S 24-Feb-11 1:48am

Good answer. As usual. 5. :)

Sergey Alexandrovich Kryukov 24-Feb-11 1:50am

Thank you.
--SA

Nuri Ismail 24-Feb-11 3:20am

Great explanation! 5+

Sergey Alexandrovich Kryukov 24-Feb-11 3:21am

Thank you. It needs more, but it would take more than quick answer.
--SA

Espen Harlinn 24-Feb-11 4:11am

Good points, my 5

I'll just add my 2 cents:
@Yatin Bhagat:
Sometimes it might be appropriate to silently, catch exceptions and continue execution, but that's very rare. Whenever you feel like doing this, carefully think through the consequences – at least consider logging the exception information

Sergey Alexandrovich Kryukov 24-Feb-11 12:52pm

Thank you, Espen.
Carefully also mean all such places should be documented.
I want to clarify: "silent" exception and blocking of propagation are different things. When blocking is really the last resort (it happens), exception processing can be not silent, you may want to log the condition, etc.
--SA