Browse by Tags

Tagged Content List
  • Blog Post: New for Visual Studio 2008 SP1 and FxCop 1.36 – Multi-targeting rule

    I've just published a post over my blog about a new feature we added for Visual Studio 2008 SP1 and FxCop 1.36. New for Visual Studio 2008 SP1 and FxCop 1.36 – Multi-targeting rule
  • Blog Post: Tutorial on writing your own Code Analysis rule

    Jason Kresowaty has posted a great tutorial on writing Code Analysis/FxCop rules . He also spends time on explaining parts of the Introspection API, including the different nodes and their relationship to each other. It's a great read, even if you've written some Code Analysis rules before. Definitely...
  • Blog Post: FAQ: Which Code Analysis rules shipped in which version?

    In response to a lot of recent requests, we've put together a complete list of rules that shipped in the different versions of Visual Studio Code Analysis and FxCop. Attached is an Excel worksheet providing this information for Visual Studio 2005, Visual Studio 2008, FxCop 1.35 and FxCop 1.36 Beta. ...
  • Blog Post: Reporting Code Analysis Defect Counts

    Code analysis defect counts are available in the cube that is part of the TFS Data Warehouse . This post shows you how to hook up Excel to show code analysis counts in a pivot table . First off you need to connect Excel up to the data warehouse that has the data. Under the Data tab in Excel select From...
  • Blog Post: Come chat with the Code Analysis team tomorrow

    Join members of the Visual Studio Team System product group to discuss features available in Team Foundation Server, Team Suite, Architecture Edition, Development Edition, Database Edition, and Test Edition. In addition, discuss what's new for these editions for Visual Studio 2008. We will be holding...
  • Blog Post: Try the Code Analysis Rule Sets Feature in the November "Rosario" November 2007 CTP

    We have a great new feature that we are previewing in Microsoft® Visual Studio® Team System code name “Rosario” November 2007 CTP .  This feature allows you to select pre-defined sets of rules to configure code analysis as well as define your own.  To access this feature...
  • Blog Post: Positioning Code Metrics to Management

    Another question that is coming up is: How can (or should) code metrics be presented to management ? My view is that in all cases the metrics are something that can help make decisions around focus and prioritization. Management should be made aware of the metrics and what they mean to allow them to...
  • Blog Post: Maintainability Index Range and Meaning

    Another question: The maintainability index has been re-set to lie between 0 and 100. How and why was this done? The metric originally was calculated as follows: Maintainability Index = 171 - 5.2 * ln(Halstead Volume) - 0.23 * (Cyclomatic Complexity) - 16.2 * ln(Lines of Code) This meant that...
  • Blog Post: Code Metrics as Check-in Policy

    This is the first in a series of posts around questions I am getting asked related to code metrics. One question that is coming up is: Can a check-in policy be defined based on code metrics in TFS? Well, code metrics itself does not have a check-in policy but fortunately the Maintainability...
  • Blog Post: Code Metrics Customization

    A number of people have asked: Is there a way to customize the existing code metrics or add additional ones? The simple answer at this time is No.  There are no extension points or customizations available at this time for code metrics.  This feature was added late in the cycle for VS 2008...
  • Blog Post: New for Visual Studio 2008 - Code Metrics

    While we've already briefly spoken about Code Metrics when we announced it , I thought I would discuss it in a little more depth, in particular the metrics it provides. As mentioned previously, Code Metrics is a new tool window that helps users find and act upon complex and unmaintainable areas within...
  • Blog Post: New for Visual Studio 2008 - The 'Analyze' menu

    While Ian Huff has already talked about the new 'Developer' menu that has been added to Visual Studio 2008, I thought I would briefly mention some of the changes to it that were made between Beta 2 and RTM. For those that have yet to see this menu, similar to the existing Test menu, we've added a...
  • Blog Post: New for Visual Studio 2008 - Support for anonymous methods and lambda expressions

    One of my favorite new features for Code Analysis in Visual Studio 2008 is our support for analyzing anonymous methods and lambda expressions. While anonymous methods have been around in C# since Visual Studio 2005, lambda expressions are new for both C# and Visual Basic in Visual Studio 2008. For...
  • Blog Post: New for Visual Studio 2008 - Code Analysis Policy improvements

    One not very well known feature that lights up when connected to a Team Foundation Server, is the ability to enforce that Code Analysis be run before every check-in. Called a Code Analysis Policy , this feature allows your team to find and fix Code Analysis warnings earlier in the product cycle rather...
  • Blog Post: New for Visual Studio 2008 - Custom Dictionaries

    Once you turn on the new spelling rules that we've added to Visual Studio 2008, you will want to start to customize the words that it fires on; this is where the new custom dictionary support comes in. A custom dictionary in its basic form, similar to the concept in Microsoft Word, allows you to silence...
  • Blog Post: New for Visual Studio 2008 - Spelling rules

    Surprisingly, one the biggest requests for Code Analysis in Visual Studio 2005 was to include the spelling rules that shipped with the FxCop standalone. We had Microsoft consultants tell us that they actually had trouble moving some customers from FxCop to Code Analysis because they were not included...
  • Blog Post: $(CodeAnalysisTreatWarningsAsErrors) MSBuild property

    For Visual Studio 2008, we have added a new MSBuild property that allows you to easily treat all Code Analysis warnings as build errors. This can be useful for example, if you want to force that any firing of a Code Analysis rule to break the build during a nightly Team Build without needing to individually...
  • Blog Post: Come chat with the Code Analysis team (and Team System) team - tomorrow

    Join members of the Visual Studio Team System product group to discuss features available in Visual Studio Team Foundation Server, Architecture Edition, Development Edition, Database Edition, and Test Edition. In addition, discuss what's new in Visual Studio 2008 Beta 2 . We will be holding two sessions...
  • Blog Post: Come chat with the Team System product team tomorrow

    Join members of the Visual Studio Team System product group to discuss features available in Visual Studio Team Foundation Server, Team Editions for Architects, Developers, Database Pros, and Testers. In addition, discuss what's new in the upcoming Orcas CTP. We will be holding two sessions: Join...
  • Blog Post: 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 Code Analysis enforces, only contains...
  • Blog Post: Visual Studio 'Orcas' Beta 1 Released!

    If you've been living under a rock (or just distracted by this Silverlight thingy), you might have missed that we've released Beta 1 of Visual Studio 'Orcas' . This release include a number of changes to Code Analysis when compared to Visual Studio 2005, including Code Metrics , generated code improvements...
  • Blog Post: Correct usage of the CompilerGeneratedAttribute and the GeneratedCodeAttribute

    Both Code Analysis, FxCop and Code Metrics make extensive use of CompilerGeneratedAttribute and GeneratedCodeAttribute to distinguish between user-written code and tool and compiler generated code. The following describes this behavior: Code Analysis in Visual Studio 2005 and FxCop 1.35 ...
  • Blog Post: Code Analysis (Team System) Chat - This Friday

    Update: We've added another session for Asia and the Pacific. Join members of the Visual Studio Team System product group to discuss features available in Visual Studio Team Foundation Server, Team Editions for Architects, Developers, Database Pros, and Testers. In addition, discuss what's new...
  • Blog Post: Announcing Visual Studio Code Metrics!

    Announcing the new Code Metrics feature for Visual Studio ‘Orcas’! Available in Visual Studio Team Developer and Team Suite, this new feature allows users to generate code metrics for projects and solutions and displays the results in the Code Metrics Results tool window: As you can see above,...
  • Blog Post: Framework for intergrated FxCop rule testing

    Roy Osherove has put together a Framework for testing FxCop rules . It's an interesting approach, firing up the FxCop engine for each rule that he wants to test. There are few things that I would like to see it support: The ability to specify positive tests (code that rules should not fire when...
Page 1 of 2 (29 items) 12