Welcome to MSDN Blogs Sign in | Join | Help

April 2006 - Posts

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

FxCop Chat - This Wed @ 10 AM

Update: The transcript for this chat can be found here . Join the chat on April 19th, 2006 10:00am - 11:00am Pacific time. Our team, Team System Developer and Tester Tools (Unit Testing, Web Testing, Load Testing, Profiling, Code Analysis (FxCop and PREFast)

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: How do I access the locals of a method in a custom rule? [Michael Fanning, David Kean]

Note: The custom rules API is likely to change in the next version of FxCop/Visual Studio. Currently, the locals of a method are stored in a pseudo-instruction in the method's InstructionList. We plan to change this in a future version of the tool and

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

FAQ: How do I indicate to DoNotDeclareReadOnlyMutableReferenceTypes that a type is immutable? [David Kean]

DoNotDeclareReadOnlyMutableReferenceTypes is a rule that checks for visible read-only fields that are mutable reference types (classes). A mutable type is a type whose instance data can be changed once it has been constructed. For example, the following

FxCop 1.35 RC1 online

Last week we had a push to fix many of the issues reported on the forum and include them in the FxCop 1.35 release. 32 bugs later, we have a release candidate ready. The code changes between FxCop 1.35 Beta 1 and RC 1 range from simple bugs such as updating
Posted by JeffVa | 12 Comments
 
Page view tracker