Error Handling Best Practices .net
Articles Technical Blogs Posting/Update Guidelines Article Help Forum Article Competition Submit an article or tip Post your Blog quick answersQ&A Ask a Question about this article Ask a Question View Unanswered Questions View All Questions... C# questions Linux questions ASP.NET questions SQL questions VB.NET questions discussionsforums All Message Boards... Application Lifecycle> Running a Business Sales / Marketing Collaboration / Beta Testing Work Issues Design and Architecture ASP.NET JavaScript C / C++ / MFC> ATL / WTL / STL Managed C++/CLI C# Free Tools Objective-C and Swift Database Hardware & Devices> System Admin Hosting and Servers Java .NET Framework Android iOS Mobile SharePoint Silverlight / WPF Visual Basic Web Development Site Bugs / Suggestions Spam and Abuse Watch features Competitions News The Insider Newsletter The Daily Build Newsletter Newsletter archive Surveys Product Showcase Research Library CodeProject Stuff communitylounge Who's Who Most Valuable Professionals The Lounge The Insider News The Weird & The Wonderful The Soapbox Press Releases Non-English Language > General Indian Topics General Chinese Topics help What is 'CodeProject'? General FAQ Ask a Question Bugs and Suggestions Article Help Forum Site Map Advertise with us About our Advertising Employment Opportunities About Us Articles » Development Lifecycle » Best Practices » General Coding ArticleBrowse CodeStatsRevisions (2)Alternatives Comments (199) Add your ownalternative version Tagged as VBC#Windows.NETDotGNUVisual-StudioVS.NET2003DevQAArchitect Stats 1.4M views1.1K bookmarked Posted 9 Feb 2005 Exception Handling Best Practices in .NET Daniel Turini, 21 Feb 2005 CPOL 4.90 (412 votes) 1 2 3 4 5 4.90/5 - 412 votes19 removedμ 4.77, σa 1.22 [?] Rate this: Please Sign up or sign in to vote. Design guidelines for exception handling in .NET which will help you to create more robust software Contents Introduction Plan for the worst Check it early Don't trust external data The only reliable devices are: the video, the mouse and keyboard. Writes can fail, too Code Safely Don't throw new Exception() Don't put important exception information on the Message field Put a single catch (Exception ex) per thread Generic Exceptions caught should be published Log Exception.ToString(); never log only Exception.Message! Don't catch (Exception) more than once per thread Don't ever swallow exceptions Cleanup code should be put in finally blocks Use "using" everywhere Don't return special values on error conditions Don't use exceptions to indicate absence of a resource Don't use exception handling as means of returning information fr
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up How http://www.codeproject.com/Articles/9538/Exception-Handling-Best-Practices-in-NET using try catch for exception handling is best practice up vote 112 down vote favorite 80 while maintaining my colleague's code from even someone who claims to be a senior developer, I often see the following code: try { //do something } catch { //Do nothing } or sometimes they write logging information to log files like following try catch block try { //do http://stackoverflow.com/questions/14973642/how-using-try-catch-for-exception-handling-is-best-practice some work } catch(Exception exception) { WriteException2LogFile(exception); } I am just wondering if what they have done is the best practice? It makes me confused because in my thinking users should know what happens with the system. Please give me some advice. c# .net exception exception-handling try-catch share|improve this question edited Feb 20 '13 at 6:45 user1645055 asked Feb 20 '13 at 6:32 Toan Nguyen 5,60731841 87 Snippet #1 is 99.999% of the time unacceptable. –leppie Feb 20 '13 at 6:33 14 Displaying exception directly to user is never a good idea mainly for two reasons: 1. if it's usual user (s)he will be annoyed reading error message that tells very few for him/her. 2. if (s)he's, so called, hacker (s)he may get useful information. The best practice, IMO, is to log exception and show friendly error message. –Leri Feb 20 '13 at 6:35 3 @leppie If something unexpected occurs (like NullReference or ArgumentNull that is not part of application flow) it means that there's a bug that needs to be fixed so logging them will help to debug your code much faster. –Leri Feb 20 '13
Websites Community Support ASP.NET Community Standup ForumsHelp Web Forms:Guidance Videos Samples Forum Books Open Source Getting Started Getting StartedGetting Started with ASP.NET https://www.asp.net/web-forms/overview/getting-started/getting-started-with-aspnet-45-web-forms/aspnet-error-handling 4.5 Web Forms and Visual Studio 20131. Getting Started with Web Forms and Visual Studio2. Create the Project3. Create the Data Access Layer4. UI and Navigation5. Display Data Items and Details6. Shopping Cart7. Checkout and Payment with PayPal8. Membership and Administration9. URL Routing10. ASP.NET Error HandlingIntroduction to ASP.NET Web FormsCreating a Basic Web Forms Page in Visual Studio error handling 2013Creating ASP.NET Web Projects in Visual Studio 2013Code Editing ASP.NET Web Forms in Visual Studio 2013ASP.NET Scaffolding in Visual Studio 2013ASP.NET Web Forms (dotnetConf 2014)Using Page Inspector for Visual Studio 2012 in ASP.NET Web FormsVisual Studio 2012 Hands On LabsWhat's New in ASP.NET and Web Development in Visual Studio 2012What's New in Web Forms in ASP.NET 4.5Using error handling best Page Inspector in Visual Studio 2012Monitoring and TelemetryRoutingASP.NET 4 - RoutingASP.NET 4 - Defining RoutesASP.NET 4 - Constructing URLs from RoutesASP.NET 4 - Accessing URL Parameters in a PageJavaScript and Client FrameworksASP.NET 4 - Microsoft Ajax OverviewASP.NET AJAX Control Toolkit (maintained by DevExpress)Working with Data Getting Started with ASP.NET 4.5 Web FormsModel Binding and Web Forms in Visual Studio 20131. Retrieving and Displaying Data2. Updating, Deleting, and Creating Data3. Sorting, Paging, and Filtering Data4. Integrating JQuery UI Datepicker5. Using Query String Values to Filter Data6. Adding Business Logic LayerASP.NET 4 Web Forms - Validating User Input in a PageASP.NET 4 Web Forms - State ManagementASP.NET Data Access - Recommended ResourcesServer Data ControlsASP.NET 4 Data-Bound ControlsASP.NET 4 Data Source Controls OverviewASP.NET 4.5 Chart ControlRecommended Resources for ASP.NET Data AccessSecurity, Authentication, and Authorization Getting Started with ASP.NET 4.5 Web FormsASP.NET IdentityCreate a secure ASP.NET Web Forms app with user registration, email confirmation and password reset (C#)Create an ASP.NET Web Forms app with SMS Two-Factor Authentication (C#)OWIN and KatanaPerformanceUsing Asynchronous Methods in ASP.NET 4