FxCop (Team System) MSDN Chat Roundup

Update: The transcript for this chat can be found here.  Yesterday we had a really successful Team System chat with over 150 customers (including 7 MVPs). Thank you to all that attended, it is really great to be able to speak to customers directly. The following is a list of questions that were asked about FxCop/Managed Code Analysis:…


FxCop (Team System) MSDN Chat

Update: The transcript for this chat can be found here.   Come and join members from the Visual Studio Team System product group to discuss features available in Visual Studio Architect, Developer and Tester editions and Team Foundation Server. There will be experts on hand to answer your questions, so we hope to see you there!…


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 Microsoft teams (and you) do with their internal types and members is completely up to them. Noise. If you tend…

4

FAQ: Why is FxCop 1.32 not available for download? [David Kean]

Update: While SharePoint Portal Server 2003 will not run side-by-side with .NET 2.0, SharePoint Portal Server 2003 SP2 will. For more information, see: http://support.microsoft.com/kb/907763. We have had a lot of users contacting us since we released FxCop 1.35, asking for a link to be able to download a copy of FxCop 1.32. There appears to be some…

11

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 -> Rules Expand the Naming Rules node and…

6

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. Support for in source suppression via the SuppressMessageAttribute* (.NET 2.0 only). New WiX-based installer Ability to search GAC for…

13

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 1FAQ: Why does FxCop warn against catch(Exception)? – Part 2FAQ: Why does FxCop warn against catch(Exception)? – Part 3 I said from the beginning that this issue is controversial, and some of your feedback certainly confirms that….

22

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 1FAQ: Why does FxCop warn against catch(Exception)? – Part 2FAQ: Why does FxCop warn against catch(Exception)? – Part 3 On Wednesday, I explained why catch (Exception) is a bad idea, and many of you replied with interesting…

28

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 1FAQ: Why does FxCop warn against catch(Exception)? – Part 2FAQ: Why does FxCop warn against catch(Exception)? – Part 3 This question comes up a lot, and I think there’s a lot of confusion and controversy about the rule….

26