Code Analysis (Team System) Chat Roundup

We had two great chats last Friday. Thank-you to all that attended, I had a lot of fun.

The following is a list of Code Analysis questions that were asked:

Code Metrics


DavidKean_MS (Moderator):
Q: JeffBe: I'm very interested in the code metrics, are these integrated into build reports though? We'd like to be able to track code metrics over time.
A: This is something that we've received a lot requests for. Unfortunately, for Orcas we won't be integrating this into TeamBuild or any sort of reports. However, this is definitely something that we want to do in a future release.

DavidKean_MS (Moderator):
Q: Where can i find more information about CyclomaticComplexity feature in Orcas ?
A: Besides what we've already published on our blog (, there's not much information around at the moment. This will change in Beta 2, we also do plan on doing more in-depth posts on the blog in the coming months.


DavidKean_MS (Moderator):
Q: I'll ask the audience. What would be your preference on something that we should focus on in Code Metrics? 1) TeamBuild integration 2) Extensibility (the ability to add your own metrics) 3) Policy Enforcement of Metrics (being able to prevent check-ins of code that doesn't pass a certain threshold of maintainability. 4) More extensive metrics


DavidKean_MS (Moderator):
Q:  Extensibility, enforcement, more extensive metrics (in that order)
A: Thanks Peter. You want to plug in your own metrics? Do you think we're missing some?


DavidKean_MS (Moderator):
Q:  metrics.  Complexity is a bit subjective--that's something that would be best suited to customization.  I'd be a big proponent of something that measures degree of Law of Demeter violations...
A: Yes we've heard that. This is one of the reasons we really want to wait to see what customization customers really want. ie Do they simply want to tweak the numbers that make up the magic 'Maintainability Index', or do they want to completely replace the metric altogether.


Code Analysis


DavidKean_MS (Moderator):
Q: Did you have to do anything special with CodeAnalysis in Orcas to support multiple versions of the .NET Framework?
A: The great thing about Orcas is that we actually get this for free. The new MSBuild mult-targeting means that you simply select the Framework you want to build against and Code Analysis  'just works'.


DavidKean_MS (Moderator):
Q: Any idea if nStatic-like features will be added to code analysis?
A: While I haven't yet played around with nStatic (I don't believe it has been released), we are looking at doing a lot more advanced analysis in a future version of Visual Studio.


DavidKean_MS (Moderator):
Q: Any added Code Analysis rules for C# 3.0 language extensions?
A: Unfortunately no. Similar to the introduction of the .NET 1.0, it’s still not very clear on the gotchas and mistakes that people make when writing Linq. With regards to the other features, such as Extension methods, Automatic Properties, etc what would you like to see?


DavidKean_MS (Moderator):
Q: The Static Analysis results are published to the data warehouse, will we ever see them in the build reports? Or is there a way to customise the build reports to include them?
A: Grant, I'm not an expert on our integration with Team Build, but I'll certainly pass this request onto them.


DavidKean_MS (Moderator):
Q:   I guess I'm out of luck on var (doesn't make it into the assembly, per se).  I know many people watching C# 3. demos are really put off by wholesale abilities of their developers to use features like extension methods.
A: It's pretty likely that you won't see any rules from us 'stating' don't use Extension methods. 😉 However, this wouldn't be too hard to write a simple rule to do this. We are thinking about releasing rule samples when Orcas releases, I'll make sure this gets chucked in.


DavidKean_MS (Moderator):
Q:  to specifically answer your question "...missing some".  Not really, other than possibly new C# 3.0 stuff.  Most of the rules would be very specific to either an in-house class library or the way one shop mandates coding/design.
A: As you know, a lot of the C# 3.0/VB 9 improvements are simply syntactic sugar over IL. So it actually makes it hard to write rules that target them. What I actually meant though, do you think we're missing some metrics?


Custom Rules


DavidKean_MS (Moderator):
Q: David: Question for you, in addition to FxCop do you think a tool similar to StyleCop will be available in the future? Although API level code analysis is great there are certain rules we'd like to enforce on non-public code constructs.
A: As you well know, FxCop/Managed Code Analysis currently runs over an assembly and not actually the source code. To change this would be a significant change. However, in saying that, this is one of many features we may consider doing in a future release, however, if we do end up doing it, it’s likely to be more a long term feature, rather than short term. For the next couple of versions at least, you will still see binary analysis.


DavidKean_MS (Moderator):
Q:   I think the greatest potential of TFS/CodeAnalysis is in customization.  Given it's something that makes it to the assembly level, for shops to be able to define their custom rules and enforce them at check-in would be a huge plus.
A: Peter we hear ya loud and clear. This is definitely something that we want to focus on in the future. The question is, do we focus on making rules more customizable or do we  focus on allow teams to write their own rules? What does everyone think?


DavidKean_MS (Moderator):
Q:  RE: customizable/rule-creation.  I think rule creation would tend to be more accepted.  Most of the shops I deal with accept most of the out-of-the-box rules and I can't think of many that could be improved by customization (bar metrics...).
A: What about naming/casing guidelines? Do you see many shops wanting to customize these or are they happy following the Design Guidelines?


DavidKean_MS (Moderator):
Q. We do having naming standards that are a subset of the Design Guideline, i.e. we've made some rules more restrictive so we would want to customise these.
A: Good to know. Will bring this to the product team.




DavidKean_MS (Moderator):
Q: Is a release of FxCop planned to coincide with the RTM of Orcas? What classes of code analysis with TFS include that FxCop won't?
A: It is likely that the next version of FxCop will be released sometime around the release of Orcas. Things that are included in Visual Studio that FxCop does not have are (but not limited to); Code Analysis Policy (the ability to enforce that code passes particular rules on check-in), Maintainability and Reliability rules, Code Metrics, out-of-the-box support for MSBuild (so warnings can be displayed in the Error List) and a few other features.


DavidKean_MS (Moderator):
Q: Are there any updates coming to FxCop 1.35? It's been a long time since release, and there are several bugs.
A: Although I can't get give an exact date, we do plan on releasing an update to FxCop sometime in the next quarter.  What bugs are you hitting?


DavidKean_MS (Moderator):
Q: The fxcop bugs are generally "rule exceptions". We have worked around some of them (disabling rules), but this is not ideal. We have 100s of projects and it is hard to manage.
A: By 'rule exceptions' do you mean crashing rules? Can you make sure that we know about these over on the Code Analysis forum ( We have fixed a lot of these since 1.35, however, I want to make sure we fixed the ones you've encountered.

Comments (2)

  1. Folks interested in FxCop should have a glance at the NDepend tool:

    NDepend analyses source code and .NET assemblies. It allows controlling the complexity, the internal dependencies and the quality of .NET code.

    NDepend provides a language (CQL Code Query Language) dedicated to query and constraint a codebase.

    It also comes from with advanced code visualization (Dependencies Matrix, Metric treemap, Box and Arrows graph…), more than 60 metrics, facilities to generate reports and to be integrated with mainstream build technologies and development tools.

    NDepend also allows to compare precisely different versions of your codebase.

  2. Cagatay Catal says:


    I’d like to see more Object Oriented metrics inside this Code Analysis tool. As I see, you only calculate Depth of Inheritance Tree metric as OO design metric. As you know, there are 5 more OO metrics from Chidamber-Kemerer (CK) metrics suite that we can calculate.CK metrics are very popular in metrics area and many tools support them.

    WMC (Weighted Method Count):

    RFC (Response for a Class):

    NOC (Number of Children):

    CBO (Coupling Between Object Classes):

    LCOM (Lack of Cohesion in Methods):

    And in 1999 Rosenberg had reported that the classes which have at least 2 features below should have to be marked as refactoring candidate.

    RFC > 100

    CBO > 5

    RFC > 5 * number of methods in class

    WMC > 100

    Number of methods > 40

    Furthermore, researchers and engineers who study on fault prediction use the Chidamber-Kemerer metrics for their models. If you can show them as DIT in orcas, it will facilitate QA team’s job.

    Last point is about integrating some fault prediction approach inside Orcas code metrics feature for future releases.

    The features you have provided are very important and useful for developers all around the world. Also, it will be very useful if you give the threshold level of each code metric.

    Thank you.

    Best wishes,


    Cagatay CATAL

    MS Computer Engineer


    Information Technologies Institute

    Gebze, Kocaeli – TURKEY


Skip to main content