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

Question Posted / .netguru

4 Answers
14150 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

Explain what benefit does your code receive if you decorate it with attributes demanding specific security permissions?

0 Answers

Why is it preferred to not use finalize for clean up?

0 Answers

What are asp.net web forms?

0 Answers

You have multiline textbox and submit button. if you paste xml content into multiline textbox and hit submit button. what action will perform?