Eddy Vluggen wrote:

Not that I know of. Well, that's a bit of a lie; you could loop through all the assemblies that are loaded, and list those classes that inherit from Exception.

Is there any way to do this?

Eddy Vluggen wrote:

The programmers should already be handling the errors that they can expect locally with a try-catch block,

My concern was about finding those sections of code which should be within a try catch block, but are not. If the exception was caught at the right location the programmer would have various options (e.g. abort,retry,ignore). Hence the emphasis on finding a formal way to identifying all code sections which can throw an exception and resolving them through a code review. A global exception handler would be my last resort at the time of actual deployment. Thanks for the reply....

JasonLee07 wrote:

Hope I'm not asking a dumb question but is the code you're executing within a try / catch block?

Some of the code is ... and some is not.... The current approach is I test various features of the application until it pop-ups an unhandled exception after which the offending piece of code is encapsulated in an try {...} catch {...} block What I was looking for is a formal method of getting a list of all possible code blocks which can throw an exception and performing a code review to ensure that all exceptions are properly handled.....

JasonLee07 wrote:

Second question is do you what is causing the exception yet?

I have root caused the exceptions which were triggered by my testcases.

I am testing a c# application and one of the issues I am finding is the application throws unhandled exception error once in a while which leads to a debug and fix cycle.... Is there a way to get a list of all possible exceptions that can be thrown by the application and the line number where it can be thrown.... Regards Ajay