Why is catch(Exception) almost always a bad idea?
Answers were Sorted based on User's Feedback
Answer / subasini
Catch(Exception) is Bad Because Of It supress your Fault in
the coding
Is This Answer Correct ? | 4 Yes | 2 No |
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 |
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 |
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 |
Where you store Connection string in "Web.Config" file in ASP.NET?
0 Answers Sans Pareil IT Services,
Difference between application events and session events
Can you explain page lifecycle in net?
what is generics?
When Cookies are expired in ASP.NET?
0 Answers Sans Pareil IT Services,
What types of data validation events are commonly seen in the client-side form validation?
What is inheritance and an how it be used, example with an example?
code for inserting images into gridview colomns from database
If you want to write your own dot net language, what steps you will you take care?
what is the differance between native code & managed code?
Explain what are the advantages of asp.net mvc framework? : asp.net mvc
what is the assembly?