Find the unhandled exceptions in your .NET application before they occur in runtime

The situation

You're developing a .NET application, and you need to ensure that your code is free from unwanted unhandled exceptions. You want end-users to experience a quality program, which isn't going to come up with generic error messages or crash. You know all too well that crashing applications can lead to a loss of data for your customers, or a loss of sales for you, and can leave a lot of people unimpressed.

Key challenges

• Identifying the possible exceptions that an application can throw before they happen.
• Locating which functions can throw which exceptions.
• Using incomplete .NET documentation and proceeding by time-consuming, trial and error processes, trying to crash your program deliberately to find those unhandled exceptions.

How we can solve it

1. Use Exception Hunter™ to locate which methods – and lines of code – can throw what type of exception.
   

   	a.	Choose the assembly to analyze.
   	b.	Drill down to the method level.
   	c.	Review the list of different types of exceptions that your methods can throw.
   	d.	Write an exception handler where needed.

2. It literally takes minutes to get to the list of possible exceptions a method can throw, and the tool enables .NET professional developers to deal with their exceptions during the development phase, rather than patching up after the application has been shipped.

Benefits of our solution

• Eliminate crashes before they happen; you don't need to wait until an error happens to find out which method throws which exceptions.
• You can get on with your work, without wasting time searching for possible exceptions by a manual trial-and-error process.
• By using Exception Hunter throughout the development phase, you'll be able to build more resilient applications you can be proud of.

Help

• Exception Hunter