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 |
Define the term Scavenging in Caching?
How to find last error which occurred in Asp.net ?
Which template must you provide, in order to display data in a Repeater control?
What is the application pool?
What tags do you need to add within the asp:datagrid tags to bind columns manually?
What is role-based security in asp.net?
What is enableviewstatemac in asp net?
What is the use of execute non query in asp.net?
What is postback in asp net?
How to save Link of a Webpage in excel sheet?
Describe the difference between a Thread and a Process?
Every Validation controls have same option ?
Visual Basic (800)
C Sharp (3816)
ASP.NET (3180)
VB.NET (461)
COM+ (79)
ADO.NET (717)
IIS (369)
MTS (11)
Crystal Reports (81)
BizTalk (89)
Dot Net (2435)
Exchange Server (362)
SharePoint (720)
WCF (340)
MS Office Microsoft (6963)
LINQ Language-Integrated Query (317)
WPF (371)
TypeScript (144)
Microsoft Related AllOther (311)