Why is catch(Exception) almost always a bad idea?

Question Posted / .netguru

4 Answers
14173 Views
I also Faced
E-Mail Answers

Answers were Sorted based on User's Feedback

Why is catch(Exception) almost always a bad idea?..

Answer / subasini

Catch(Exception) is Bad Because Of It supress your Fault in
the coding

Is This Answer Correct ?

4 Yes

2 No

Why is catch(Exception) almost always a bad idea?..

Answer / senthilselvan

if you know what kind of error may occur in that block mean
, will it be right to use catch block without handling the
proper validation?

Is This Answer Correct ?

2 Yes

1 No

Why is catch(Exception) almost always a bad idea?..

Answer / nagaraj

Catch(Exception) means that you catch all the exception
which might not occur. But, really we need to catch only
some type of exception, so we need to catch only those type
instead of catching all the exceptions.

Is This Answer Correct ?

1 Yes

0 No

Why is catch(Exception) almost always a bad idea?..

Answer / anna

it's not the bad idea of using catch exception.
catch exception catches all the exceptions in try block.
if we use these blocks, we will be able to know where the
exact error is.
if we use one try block, we must use the catch block .

Is This Answer Correct ?

6 Yes

6 No

Post New Answer

More ASP.NET Interview Questions

What is difference between asp.net and asp?

0 Answers

How do you perform validations?

3 Answers Microsoft,

In asp.net, if a webpage seems too slow to load completely in th ebrowser. In this case what are the checkings or actions you will take to rectify the slowness or which are the factors related to this issue? How we can trace it?

3 Answers

Write code to send e-mail from an asp.net application?

0 Answers

what are configuration files?

0 Answers

How to find last error which occurred in Asp.net ?

0 Answers

how we use web services

2 Answers

What is http response header?

0 Answers

Define application state variable and session state variable?