Welcome to MSDN Blogs Sign in | Join | Help

Browse by Tags

All Tags » Tips and Tricks » Configuration   (RSS)
Tuesday, May 08, 2007 8:00 AM

TIP: How to change the (Orcas) Managed Code Analysis naming/design rules to fire on internals

A while ago I mentioned that FxCop (and hence Managed Code Analysis) naming and design rules only fire on publicly visible types and members. As you may recall, there were a couple of reason for this: The .NET Framework Design Guidelines , which FxCop/Managed
Posted by David M. Kean | 1 Comments
Friday, August 11, 2006 8:00 AM

TIP: How to quickly enable Code Analysis on multiple projects [David Kean]

Daniel Fisher has posted a entry on using a macro to quickly enable Code Analysis on multiple projects . The macro also allows you to apply the same rule selections across an entire solution. Thanks Daniel!
Posted by David M. Kean | 0 Comments
Tuesday, August 08, 2006 8:56 PM

TIP: How to change the FxCop naming/design rules to fire on internals [David Kean]

By default, the FxCop naming and design rules only fire on publicly visible types and members. There are a couple reasons for this: The .NET Framework Design Guidelines , which FxCop enforces, only contains guidelines for publicly visible API. What internal
Posted by David M. Kean | 4 Comments
 
Page view tracker