C# Catching Exceptions Guideline (updated for C# 6.0)

The article proposes and summarizes guidelines for exception handling / catching exceptions.

  • AVOID catching exceptions that you’re unable to handle fully.
  • AVOID hiding (discarding) exceptions you don’t fully handle.
  • DO use throw to rethrow an exception; rather than throw inside a catch block.
  • DO set the wrapping exception’s InnerException property with the caught exception unless doing so exposes private data.
  • CONSIDER an exception condition in favor of having to rethrow an exception after capturing one you can’t handle.
  • AVOID throwing exceptions from exception conditional expression.
  • DO use caution when rethrowing different exceptions.
  • Rarely use System.Exception and general catch blocks—except to log the exception before shutting down the application.
  • AVOID exception reporting or logging lower in the call stack.


Sources:

Comments

Post a Comment

Popular posts from this blog

SQL Server Setup: Windows Firewall warning (Ports)

Image
What was it again SQL server setup throws out, when you have your Windows Firewall on?! Rule "Windows Firewall" generated a warning. The Windows Firewall is enabled. Make sure the appropriate ports are open to enable remote access. See the rules documentation at http://go.microsoft.com/fwlink/?LinkId=94001 for information about ports to open for each feature. Keywords: Setup, Firewall, Ports, SQL Server, Microsoft
Read more

Visual Studio: Scaffolding, EF and virtual

virtual properties "give EF a hook into your plain C# classes and enable features such as an efficient change-tracking mechanism. The EF needs to know when a property value on a model changes, because it might need to issue a SQL UPDATE statement to reconcile those changes with the database." Sources: Professional ASP.NET MVC 5, Chapter 4
Read more

Windows Server 2012 R2: Domain Controller Minimum Requirements & associated server roles

Quite moderate minimum requirements for the basic hardware requirements, but depending on usage (as always) the more RAM the better. Processor Minimum: Single processor with 1.4 GHz (x64 processor) or 1.3GHz (Dual Core) Memory Minimum: 512 MB RAM Disk Space Requirements Minimum: 32 GB or greater Usually the question also goes hand-in-hand with the other tasks that machine can perform: "There are certain roles that typically get folded in with the domain controller in all but the biggest networks (e.g. DNS/DHCP/WINS/Cert Server) with little harm." "There are some that get folded into a DC and will cause performance issues on all but the smallest networks (e.g. File Server/intranet server/WDS Server) but these issues are probably manageable depending on load. These previous two classes of role are a case of a balancing act, how concerned you are about performance on your DCs vs. the resources you have available to provision your network. It's b...
Read more