Should StyleCop depreciate the use of ApplicationException?

Sep 16, 2011 at 3:41 PM

Please see the framework 4.0 advice at http://msdn.microsoft.com/en-us/library/system.applicationexception%28v=VS.100%29.aspx

In particular you should note the statement "If you are designing an application that needs to create its own exceptions, you are advised to derive custom exceptions from the Exception class. It was originally thought that custom exceptions should derive from the ApplicationException class; however in practice this has not been found to add significant value. "

Should StyleCop add a rule to depreciate the use of ApplicationException or is this more properly in realm of the FXCOP team?

Coordinator
Sep 16, 2011 at 6:05 PM
That's fxcop rather than stylecop.

A.



On 16 Sep 2011, at 16:41, "TATWORTH" <notifications@codeplex.com> wrote:

From: TATWORTH

Please see the framework 4.0 advice at http://msdn.microsoft.com/en-us/library/system.applicationexception%28v=VS.100%29.aspx

In particular you should note the statement "If you are designing an application that needs to create its own exceptions, you are advised to derive custom exceptions from the Exception class. It was originally thought that custom exceptions should derive from the ApplicationException class; however in practice this has not been found to add significant value. "

Should StyleCop add a rule to depreciate the use of ApplicationException or is this more properly in realm of the FXCOP team?