DA0007: Avoid using exceptions for control flow
.NET Framework Usage
A high number of exceptions are consistently being thrown. Consider reducing the use of exceptions in program logic.
When you profile by using the sampling, .NET memory, or resource contention methods, you must collect at least 25 samples to trigger this rule.
While the use of exception handlers to catch errors and other events that disrupt program execution is a good practice, the use of exception handler as part of the regular program execution logic can be expensive and should be avoided. In most cases, exceptions should be used only for circumstances that occur infrequently and are not expected.. Exceptions should not be used to return values as part of the typical program flow. In many cases, you can avoid raising exceptions by validating values and using conditional logic to halt the execution of statements that cause the problem.
For more information see the Exception Management section of Chapter 5 — Improving Managed Code Performance in the Improving .NET Application Performance and Scalability volume of the Microsoft Patterns and Practices library on MSDN.
Double-click the message in the Error List window to navigate to the Marks view. Find the column that contains the .NET CLR Exceptions(@ProcessInstance)\# of Exceps Thrown / sec measurements. Determine if there are specific phases of program execution where exception handling is more frequent than others. Using a sampling profile, try to identify throw statements and try/catch blocks that generate frequent exceptions. If necessary, add logic to catch blocks to help you understand which exceptions are being handled most frequently. Where possible, replace frequently executed throw statements or catch blocks with simple flow control logic or validation code.
For example, if you were to find that your application was handling frequent DivideByZeroException exceptions, adding logic to your program to check for denominators with zero values will improve the performance of the application.