">
FxCop 1.35 now available (again) for download- February 29, 2008 We've just uploaded FxCop 1.35 to MSDN Code Gallery after we lost our home on GotDotNet - this is for those teams that either do not want to or just aren't ready to upgrade to FxCop 1.36 Beta. For those that are already using FxCop 1.35, you'll probably notice that we flicked the switch to cause it to prompt you to download FxCop 1.36. We've love you to download it and try it out (it can be installed side-by-side without any issues with FxCop 1.35). If you hit any bugs, issues or just have some.http://blogs.msdn.com/fxcop/archive/2008/02/29/fxcop-1-35-now-available-again-for-download... FAQ: How do I prevent FxCop 1.36 from firing warnings against generated code- February 28, 2008 I've upgraded from FxCop 1.35 to 1.36 and now FxCop has started to fire warnings against typed DataSets and other generated code. How do I turn this off The reason this is occurring is because we changed the way that FxCop analyzed generated code. Whereas previously in 1.35, FxCop would only ignore particular generated code (such as DataSets), FxCop 1.36 will now either ignore no generated code, or all generated code. The former is the default. To change this behavior and have FxCop skip over...http://blogs.msdn.com/fxcop/archive/2008/02/28/faq-how-do-i-prevent-fxcop-1-36-from-firing... What happened to the download and documentation of FxCop 1.35- February 26, 2008 Update: You can now download FxCop 1.35 directly from MSDN Code Gallery. As you many you have well noticed, GotDotNet was officially retired last month now that the last of its functionality was superceded by MSDN Code Gallery. Unfortunately, at the same time, the FxCop team page, the download for FxCop 1.35 and the rule documentation was also removed. We were told last year about the deprecation of GotDotNet and we had hoped that by now we would have had a new team site on...http://blogs.msdn.com/fxcop/archive/2008/02/26/what-happened-to-the-download-and-documenta... |