Welcome to MSDN Blogs Sign in | Join | Help

June 2006 - Posts

FxCop 1.35 rule documentation now on MSDN Wiki [David Kean]

One thing you might notice from today when you fire up FxCop 1.35 , is that the rule URLs are now redirecting to the new MSDN Library Wiki as opposed to the old docs on GotDotNet. To see this in action, try the following: Open FxCop 1.35 Choose Windows

FxCop 1.35 Released!

We are pleased to announce the release of FxCop 1.35. Please visit http://www.gotdotnet.com/team/fxcop to download it. Changes since FxCop 1.32: FxCop now only runs on .NET Framework 2.0, however, it supports analyzing all versions of .NET Framework.

FAQ: Why does FxCop warn against catch(Exception)? - Part 3 [Nick Guerrera]

This is the third installment in a three-part series on why FxCop warns against catch(Exception): FAQ: Why does FxCop warn against catch(Exception)? - Part 1 FAQ: Why does FxCop warn against catch(Exception)? - Part 2 FAQ: Why does FxCop warn against

FAQ: Why does FxCop warn against catch(Exception)? - Part 2 [Nick Guerrera]

This is the second installment in a three-part series on why FxCop warns against catch(Exception): FAQ: Why does FxCop warn against catch(Exception)? - Part 1 FAQ: Why does FxCop warn against catch(Exception)? - Part 2 FAQ: Why does FxCop warn against

FAQ: Why does FxCop warn against catch(Exception)? - Part 1 [Nick Guerrera]

This is the first installment in a three-part series on why FxCop warns against catch(Exception): FAQ: Why does FxCop warn against catch(Exception)? - Part 1 FAQ: Why does FxCop warn against catch(Exception)? - Part 2 FAQ: Why does FxCop warn against

TIP: Get more information about a rule/warning within Visual Studio [David Kean]

Did you know you can get more information about a particular rule/warning within Visual Studio; including its description, information on how to fix it, whether or not it is considered a breaking change, when or when not to suppress it and code samples?
 
Page view tracker