Is there is an alternate of throwing Exception between layers in ASP.NET C#

Question

0.00/5 (No votes)

See more:

I am having layered architecture in my project I am looking for an approach to avoid throwing exception between layers as throwing exceptions is associated with some cost always.

Is there any alternative approach for this.
Any help will be appreciated.

Posted 3-Feb-10 19:53pm

QuikGuide

Add a Solution

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)

Christian Graus · Answer 1 · 2010-02-03T20:06:00

Solution 1

The only alternative is to return some sort of error status code. I do often use code like:

if (!DataLayer.Save(myObject) // If it fails, tell the user it failed.

Posted 3-Feb-10 20:06pm

Christian Graus

Sandeep Mewara · Answer 2 · 2010-02-03T20:08:00

From the requirement you are asking, you can just remove try/catch at any layer other than UI (Automatic throw). Directly catch it in presentation layer and accordingly display it.

Though it's not suggested for 'all' scenario's. One should put it based on the need.

Further, i read a convincing article long back....
The True Cost of Exceptions[^]

Try-catch at every place is still not suggested but should not be avoided in the places where it helps.