Critical errors are called Exceptions and they are raised whenever the compiler encounters a problem with a segment of code. Example of common exceptions are divide by zero and reading a null value.
Exceptions can be managed using a try...catch...finally block of code. These will catch any errors and allow your code to handle the error and deal with them without the user's knowledge. Exception handling prevents errors from crashing applications causing data loss.
Traditionally in C, methods and functions would return the error code in the function result. A value of false or -1 usually indicated an error with the method. This caused a few problems, most notably that of returning a value back from a functions, and programmers usually did not test the result code. Also -1 or false could be the result of the function, not necessarily an error, so it was a little confusing.
In the .Net platform we have exceptions, which are System objects that represent a specific or generalised error condition.
Catching an Exception
usingSystem;
usingSystem.Collections.Generic;
usingSystem.Text;
namespace ConsoleApplication1
{
class Program
{
staticvoid Main(string[] args)
{
int x =0;
int y =0;
y =100/ x;
}
}
}
Obviously this line of code will cause a exception as you cannot divide any number by 0. If left like this the program will crash and stop working, requiring the user to reload the application. The solution to this is to implement a try...catch...finally block.
Try, catch and finally are three essential code blocks for problem free programs. The logic of the block is that we try to do x, catch an error if one occurs, and finally do y.
If an exception is raised in the try block then the code in the catch block is run. The catch block could call logging or reporting methods, corrective actions or alternative code. Code in the finally block is always executed regardless of an error or not. This block should close files or connections, free memory etc...
Using the divide by zero error above, with a try...catch block implemented it now looks like this.
usingSystem;
usingSystem.Collections.Generic;
usingSystem.Text;
namespace ConsoleApplication1
{
class Program
{
staticvoid Main(string[] args)
{
int x =0;
int y =0;
try
{
y =100/ x;
}
catch
{
Console.WriteLine("There was an error but we caught it!");
Console.WriteLine("Please enter a new number:");
y =int.Parse(Console.ReadLine());
}
}
}
}
Should an error occur within the try block, in this example y = 100 / x, the code within the catch block will be executed, in which you should attempt to fix the problem, notify or log the error and gracefully exit the program if required.
Let's have a look at a different example, and see what code gets executed and what code is skipped over. We will also see the finally block in action. In the first example there is no error handling.
usingSystem;
usingSystem.Collections.Generic;
usingSystem.Text;
usingSystem.IO;
namespace ConsoleApplication1
{
class Program
{
staticvoid Main(string[] args)
{
string filename ="c:\sharpertutorials\orders.csv";
StreamReader myFile =new StreamReader(filename);
string orders = myFile.ReadToEnd();
myFile.Close();
Console.WriteLine(orders);
}
}
}
When executed, the file path does not exist, so when we try and open the file an exception is raised.
As soon as the error occurs, the program cannot continue to run, the user is presented with a horrible error message and the program is forced to close. Not a very good impression.
A better solution is to use a try...catch block to handle the error.
usingSystem;
usingSystem.Collections.Generic;
usingSystem.Text;
usingSystem.IO;
namespace ConsoleApplication1
{
class Program
{
staticvoid Main(string[] args)
{
string filename ="c:\sharpertutorials\orders.csv";
string orders =string.Empty;
StreamReader myFile =null;
try
{
myFile =new StreamReader(filename);
orders = myFile.ReadToEnd();
myFile.Close();
}
catch
{
Console.WriteLine("Sorry, an error has occurred.");
}
Console.WriteLine(orders);
}
}
}
Notice how the variable declarations have been taken outside the try block. This is because we need the variables to be in the scope of the method not just the code block.
When the code is now run, the screen shows a friendly, but rather unhelpful, error message. Luckily there is a solution to this problem! The catch block can take in a parameter which will hold details about the error, so in our example a DirectoryNotFoundException was raised.
namespace ConsoleApplication1
{
class Program
{
staticvoid Main(string[] args)
{
string filename ="c:\sharpertutorials\orders.csv";
string orders =string.Empty;
StreamReader myFile =null;
try
{
myFile =new StreamReader(filename);
orders = myFile.ReadToEnd();
myFile.Close();
}
catch(DirectoryNotFoundException ex)
{
Console.WriteLine("Sorry, the path to '"+ filename +"' does not exist. Please correct the error and try again.");
}
Console.WriteLine(orders);
}
}
}
Now when the program is run the user have a detailed message telling them what the error is and how to fix it. Let's fix the error by creating the directory and re-run the program.
Another unhandled exception! This time the orders.csv file does not exist and we have a FileNotFoundException. We can implement multiple catch blocks, one for each type of exception we want to capture.
usingSystem;
usingSystem.Collections.Generic;
usingSystem.Text;
usingSystem.IO;
namespace ConsoleApplication1
{
class Program
{
staticvoid Main(string[] args)
{
string filename ="c:\sharpertutorials\orders.csv";
string orders =string.Empty;
StreamReader myFile =null;
try
{
myFile =new StreamReader(filename);
orders = myFile.ReadToEnd();
myFile.Close();
}
catch(DirectoryNotFoundException ex)
{
Console.WriteLine("Sorry, the path to '"+ filename +"' does not exist. Please correct the error and try again.");
}
catch(FileNotFoundException ex)
{
Console.WriteLine("Sorry, the file '"+ filename +"' does not exist. Please create the file and try again.");
}
Console.WriteLine(orders);
}
}
}
This time the user will get another message telling them the cause of the problem and the solution. Now we have a valid file and path, let's try and do something with the data read in from the file.
usingSystem;
usingSystem.Collections.Generic;
usingSystem.Text;
usingSystem.IO;
namespace ConsoleApplication1
{
class Program
{
staticvoid Main(string[] args)
{
string filename ="c:\sharpertutorials\orders.csv";
string orders =string.Empty;
string data =string.Empty;
StreamReader myFile =null;
try
{
myFile =new StreamReader(filename);
orders = myFile.ReadToEnd();
data = orders.Substring(0, 1);
myFile.Close();
}
catch(DirectoryNotFoundException ex)
{
Console.WriteLine("Sorry, the path to '"+ filename +"' does not exist. Please correct the error and try again.");
}
catch(FileNotFoundException ex)
{
Console.WriteLine("Sorry, the file '"+ filename +"' does not exist. Please create the file and try again.");
}
Console.WriteLine(data);
}
}
}
Again, we have another error! Because the file was empty and we tried to do a substring on an empty string we get a ArgumentOutOfRangeException and the program will force close. It gets worse though, since we have opened a file and the program has closed before we closed it! This can lead to all kinds of trouble, even more so if it was a database we were connecting to. The solution is the finally block. Code in the finally block is always guaranteed to run so we can use that to close any files or connections.
usingSystem;
usingSystem.Collections.Generic;
usingSystem.Text;
usingSystem.IO;
namespace ConsoleApplication1
{
class Program
{
staticvoid Main(string[] args)
{
string filename ="c:\sharpertutorials\orders.csv";
string orders =string.Empty;
string data =string.Empty;
StreamReader myFile =null;
try
{
myFile =new StreamReader(filename);
orders = myFile.ReadToEnd();
data = orders.Substring(0, 1);
}
catch(DirectoryNotFoundException ex)
{
Console.WriteLine("Sorry, the path to '"+ filename +"' does not exist. Please correct the error and try again.");
}
catch(FileNotFoundException ex)
{
Console.WriteLine("Sorry, the file '"+ filename +"' does not exist. Please create the file and try again.");
}
finally
{
myFile.Close();
}
Console.WriteLine(orders);
}
}
}
There we have a complete functioning try...catch...finally block. Hopefully you can see how and why this is an essential part of trouble free programming and how it can be used to avoid unhelpful and meaningless error messages.
Raising or Throwing an Exception
Exceptions can be manually thrown in your code, either for testing or to signal a fault that needs to be dealt with. It is important to validate inputs and notify errors, especially when dealing with untrusted code - such as that developed by another programmer. In this example the scenario is that we are developing a class to handle mathematical operations. Another developer will be using this class in their program. For simplicity I have included both classes in the same project.
usingSystem;
usingSystem.Collections.Generic;
usingSystem.Text;
usingSystem.IO;
namespace ConsoleApplication1
{
// Writen by us
staticclass MyMathClass
{
publicstaticdecimal Divide(int x, int y)
{
return x / y;
}
}
// Writen by somebody else
class Program
{
staticvoid Main(string[] args)
{
Console.WriteLine(MyMathClass.Divide(10, 0));
}
}
}
Here we can see that our class and method are fine. It will divide the first parameter by the second. What can go wrong? Well the other programmer is an "untrusted" source. They can pass in a valid number that causes our code to crash. In this example a divide by zero error. Since our code is the one that crashed, the fault and blame is ours.
What we can do to avoid this is validate the inputs and raise an exception that will be handled by their code. This means that if they pass in invalid data to our method, their code is at fault leaving us blame free. Raising an exception is done using the throw keyword. For a list of available exceptions you can throw, please click on Debug menu -> Exceptions... or press Ctrl+D, E. You can also create your own exceptions in the next section.
You can either throw a new exception or use the default message, or you can specify a more specific error message in the constructor, as shown below.
usingSystem;
usingSystem.Collections.Generic;
usingSystem.Text;
usingSystem.IO;
namespace ConsoleApplication1
{
// Writen by us
staticclass MyMathClass
{
publicstaticdecimal Divide(int x, int y)
{
if(y ==0)
thrownew ArgumentOutOfRangeException("Parameter y cannot be 0!");
return x / y;
}
}
// Writen by somebody else
class Program
{
staticvoid Main(string[] args)
{
Console.WriteLine(MyMathClass.Divide(10, 0));
}
}
}
Now when the program is run the calling method will receive an ArgumentOutOfRangeException message with our custom error message.
Custom Exceptions
If there is not a predefined exception that suits your needs, you can easily create a new custom exception by simply creating a class that inherits from any of the predefined exception classes or the base Exception class. They can be used in the same way as a normal exception.
class myException :System.Exception
{
}
class Program
{
staticvoid Main()
{
thrownew myException("Custom Exception");
}
}
Exception Guidelines
When throwing exceptions you should avoid exceptions for normal or expected cases. These should be handled through proper program logic.
Never create and throw objects of class Exception, it's much better to throw exceptions of the most specific class possible as it will give you greater flexibility in catching the exception and handling it. Should an unhandled exception occur, the more specific exception class will give you a better idea of where to start debugging. You should also include a description string in an Exception object with details about the error.
When catching exceptions, arrange catch blocks from specific to general otherwise the general exception will always be caught and the specific catch blocks will never be processed. Do not let exceptions go unhandled in the Main method as this will cause the application to crash and the user will not be able to recover from the error.
Never use an empty catch block - what is the point?
try
{
x =new StreamReader(filename);
}
catch
{
}
Console.WriteLine(x.ReadToEnd());
More Tutorials in C# Programming
- What is C#?
- Your First Console Application
- Data Types, Variables and Casting
- Introducing Methods and the Main() Method
- Flow Control and Entry Points
- Using the Visual Studio Debugger
- Using Method Parameters and Return Values
- Access Modifiers and Scope
- Introducing Classes and Structs
- What are Namespaces?
- Interfaces and Classes
- Conditional Statements
- Looping and Iteration in C#
- Using Arrays and Lists in C#
- Constants and Read Only Variables
- Advanced Data Types
- Error and Exception Handling in C# ⇦ You Are here
- Using Properties and Indexers
- Using Recursion in C#
- Event Handling and Delegates
- Method Overloading and Overriding
- C# Operator List
- Class Inheritance
- Class Abstraction and Encapsulation
- Aggregation and Advanced Scope Techniques
- Class and Method Attributes Explained
- Class Constructors and Destructors
- Polymorphism in C#
- Boxing and Unboxing Value Types in C#
- Operator Overloading
- Creating Multithreaded Applications with C#
- Unsafe Code Execution in Microsoft .Net
- Generic Variables
- XML Serialization and Deserialization
- C# String Formatting Examples
