Welcome to MSDN Blogs Sign in | Join | Help

Browse by Tags

All Tags » Framework Desig... » Rules   (RSS)

How to Design Exception Hierarchies

Krzysztof Cwalina, owner of the Framework Design Guidelines , has written a great post on designing exception hierarchies . He gives a great overview on the different categories of exceptions, which are placed under two main buckets he calls usage and

FAQ: Why does DoNotExposeGenericLists recommend that I expose Collection<T> instead of List<T>? [David Kean]

DoNotExposeGenericLists fires when I publicly expose List<T> via a field, method, property, or parameter. Why? Although Krzysztof briefly touched on this last year , we wanted to expand on this a little through the use of examples. The first reason

Seen any Microsoft produced code that doesn't pass Code Analysis/FxCop? [David Kean]

As some of you may already know, the majority of the Developer Division is currently planning features to be included in the next version of Visual Studio (Orcas). As part of this planning phase, the Managed Code Analysis (FxCop) team is beginning to

FAQ: Why do some sources recommend extending ApplicationException while FxCop does not? [Michael Fanning, David Kean]

TypesShouldNotExtendCertainBaseTypes fires on types that derive from ApplicationException and DoNotRaiseReservedExceptionTypes on members that throw ApplicationException. Why? There are several outdated documents floating around on the web (some orginally
 
Page view tracker