Code Analysis Team Blog

Sin duda, una de las herramientas que más me llamó la atención cuando la conocí era NDepend, una de las

Сьогодні вийшов Visual Studio Orcas - March 2007 CTP. Зкачати його можна тут . Але це мабуть не цікаве,

Cool!

last year, i wrote a tool like this, using the

CCI-Assembly from FxCop!

i think it is the same ?

Suggestion/metrics that i want use

-counter: try/finally

-counter: try/catch

-counter: try/catch with reThrow

-counter: tryCatch without Catch-Code

-Counter: Usage of Assert

-Lines of code vs. Lines of Non-Code (using CCI and pdb)

+ many idea from the (german) book: "Code-Quality-Management" (ISBN 3-898643883)

CodeRush! has had this for quite sometime.  It shows up as a little red number next to the function so you can see it while you are editting.

Its good to see that Visual Studio is going to have Metric that we can track over time (hopefully).

How nice...

Microsoft reskinned FXCop and NDepends for us.

Any chance that Rico Mariani's metrics for the framework could be integrated in some way as well, to show potentially 'fat' functions?

Kevin

The tool NDepend has support for many metrics.

http://www.ndepend.com/Metrics.aspx

Also results can be visualized in a treemap, and sifted with a dedicated language that looks like SQL:

SELECT METHODS FROM NAMESPACE "MyNamespace" WHERE CyclomaticComplexity > 20 OR NbLinesOfCode > 50

A dependency structure matrix allows to browse coupling between assemblies/namespaces/classes/members

Soon, NDepend will allow to see differences between 2 builds.

Integrating with Team Build would be great! I think being able to do build-to-build comparisons and trending would be very helpful.

Will there be an "extension" interface that allows us to develop our own metrics that can plug in to this framework?

Integration into Team build is a must, so we can report and trend this over time.  Integration with VSTS work items would be cool so we can do things like relate # of bugs to cyclomatic complexity or LOC.

Lines of code/lines of comments is important.

For ASP.Net, lines of JS and lines of HTML.

Would be nice if it worked for VSTS for DB to get # of SQL loc.

Will this be available in Orcas "Professional" (ie not just the $10K+ Team products.)?  I was disappointed that FxCop was only available integrated in Team System.  I think things like this should be seen as an important learning aid, much like intellisense.  Come to think of it, will MS be keeping the same Express/Standard/Pro/Team lineup for Orcas?

Please add this for unmanaged C++! The whole world is not managed code folks.

I was just creating some screenshots on Code Metrics in Orcas when I saw the fxcop feed getting bold

"Lines of code/lines of comments is important"

On that note, a statement count would be good to have (I use a lot of lines for single statements, so my line count is skewed)

I'd also like to see some kind of metric corresponding to the amount of exceptions that are explicitly thrown in code (even references) but not caught anywhere..it's been one I've wanted for a while (ties into XML documentation of exceptions, as well)

Maybe some security metrics as well, such as some kind of safety profile based on number of unmanaged calls, requested permissions that go unused, etc.

C'est énorme (enfin je trouve :-)) : Les fonctionnalités d'analyse de code de Visual Studio Team Edition

Are these metrics based on the individual languages or the generated MSIL?

Nice, it's great there's a GUI for this stuff now.  Great work.

Aardvark,

Can you post a bug report with a repro project over on http://connect.microsoft.com/VisualStudio?

Regards

David

I can relate to so many of the posts. I like the metrics but it should be incorporated into Code Analysis such that the build will fail if you are not within acceptable ranges. The problem with making it an optional tool is some developers in my group will use it, but others will not. This is a way to enforce good programming practices.

My general opionion of the Microsoft suite of tools is that you do not provide enough functionality. It always seems like 80% of the functionality is there but your always waiting for the other 20% (ie sharepoint, ajax, continuous integration, code analysis etc)

I've become frustrated with the "in the next version" mentality and will not spend my time integrating partial products or searching for the small amount of documentation that exists to write some custom processes. If you don't include all of the necessary functionality I'll look elsewhere.

The Visual Studio Code Analysis Team has added code metrics to Visual Studio. You can read their original

Surprise! (not the good kind) If you use FxCop or Visual Studio Static Analysis and haven't yet started

If you've been living under a rock (or just distracted by this Silverlight thingy), you might have missed

C'est énorme (enfin je trouve :-)) : Les fonctionnalités d'analyse de code de Visual Studio Team Edition

In Visual Studio 2005, we integrated a couple of internal static analysis tools - FxCop and PREfast into

It seems to me pay day cash advance payday loan klingelt�ne f�r handys

Todo list

Source Monitor Custom MSBuild Task