Announcing Visual Studio Code Metrics!

Métricas de codificación

O bruxo mobile — Wed, 28 Feb 2007 20:35:58 GMT

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

re: Announcing Visual Studio Code Metrics!

Evan Reiser — Wed, 28 Feb 2007 21:05:34 GMT

Very Cool

Метріки коду в новій CTP Orcas

Mike Chaliy's Blog — Wed, 28 Feb 2007 21:38:13 GMT

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

re: Announcing Visual Studio Code Metrics!

chris — Thu, 01 Mar 2007 00:32:37 GMT

how do you derive the "manageability index"?

re: Announcing Visual Studio Code Metrics!

Werner — Thu, 01 Mar 2007 09:04:47 GMT

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)

re: Announcing Visual Studio Code Metrics!

Grant Holliday — Thu, 01 Mar 2007 09:40:05 GMT

Will the code metrics integrate into Team Build? Will we be able to report against them?

re: Announcing Visual Studio Code Metrics!

David M. Kean — Thu, 01 Mar 2007 09:54:31 GMT

Chris: Maintainability Index is based on Halstead metrics. In future CTPs, you will see that we've made the number a little more friendly, with a range between 1 and 100.

Werner: Thanks for the feedback. Obviously, it looks like users would like a lot more metrics than the 5 we provide so far.

Grant: Not in the CTP. Is this something you would want to compare build-to-build and track over time?

re: Announcing Visual Studio Code Metrics!

Ranju. V — Thu, 01 Mar 2007 10:24:55 GMT

Any chance of this making it into VS 2005?

re: Announcing Visual Studio Code Metrics!

John Bergman — Thu, 01 Mar 2007 10:28:59 GMT

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).

Code metrics available in Orcas March CTP

Raymond Lewallen [MVP] — Thu, 01 Mar 2007 17:11:28 GMT

The FxCop team announced that the new CTP of Orcas now has code metrics . I have the VPC setup for the

re: Announcing Visual Studio Code Metrics!

GoodSyntax — Thu, 01 Mar 2007 17:38:32 GMT

How nice...

Microsoft reskinned FXCop and NDepends for us.

re: Announcing Visual Studio Code Metrics!

hessie — Thu, 01 Mar 2007 17:50:17 GMT

That's a really great feature!

But I guess it is only available with managed code?

I'd really love to do this with C++ also, as I got a huge codebase there...

re: Announcing Visual Studio Code Metrics!

Kevin I — Thu, 01 Mar 2007 18:10:04 GMT

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

Kevin

re: Announcing Visual Studio Code Metrics!

David M. Kean — Thu, 01 Mar 2007 18:29:26 GMT

Ranju: This won't make it into Visual Studio 2005, only 'Orcas'.

John: Unfortunately, there is no overlay on the editor. What would you like to see around this? Perhaps something similar to the code coverage overlay?

hessie: This is only for managed code, including C#, Visual Basic and C++/CLI.

Kevin: That's a really awesome idea. Expect to some of Rico's work in some other form in the future.

re: Announcing Visual Studio Code Metrics!

Patrick Smacchia — Thu, 01 Mar 2007 18:44:30 GMT

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.

re: Announcing Visual Studio Code Metrics!

Jasmine — Thu, 01 Mar 2007 19:25:56 GMT

"This won't make it into Visual Studio 2005, only 'Orcas'."

...then who cares? Give me something I can use. Tooting your own horn about stuff that isn't available yet is starting to really drive me nuts (with the whole industry). Don't announce products that aren't ready yet!

re: Announcing Visual Studio Code Metrics!

David M. Kean — Thu, 01 Mar 2007 19:48:35 GMT

Jasmine: I understand how you feel, I was a customer of Microsoft just over a year ago. However, we announce and provide you an early look at these features so that you can have an impact on them. Once the feature has been released, it's too late to fix bugs and broken designs. The early we release these, the more time we have to react to customer feedback.

However, stayed tuned, we will still continue to provide tips and information that you can use today in both Visual Studio 2005 and FxCop 1.35.

Code metrics in VS "Orcas"

Daniel Moth — Fri, 02 Mar 2007 02:31:49 GMT

Code metrics in VS "Orcas"

re: Announcing Visual Studio Code Metrics!

Scott — Fri, 02 Mar 2007 06:39:31 GMT

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?

re: Announcing Visual Studio Code Metrics!

Anthony Towry — Fri, 02 Mar 2007 08:22:04 GMT

This is a very cool feature that's long overdue. I'm not sure how much I like the overlay idea though at least not on by default.

re: Announcing Visual Studio Code Metrics!

Cleve Littlefield — Fri, 02 Mar 2007 12:07:16 GMT

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.

re: Announcing Visual Studio Code Metrics!

Wayne M. — Fri, 02 Mar 2007 16:32:33 GMT

So how do they get a CCM of 0? A 1 indicates a straight line function with no branches and loops. Why does the CCM have two decimal places? CCM gives an integral result.

re: Announcing Visual Studio Code Metrics!

Daniel — Fri, 02 Mar 2007 16:42:44 GMT

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?

VSTS Links - 03/02/2007

Team System News — Fri, 02 Mar 2007 18:13:13 GMT

Buck Hodges on Schema for the WorkspaceMapping.xml file. Michael Ruminer on TFS Event Subscription...

re: Announcing Visual Studio Code Metrics!

David M. Kean — Fri, 02 Mar 2007 18:52:59 GMT

Wayne: Cyclomatic Complexity of 0 means that there is no code within a type. We have fixed the decimal places and the rollups in later builds.

New and Notable 147

Sam Gentile — Fri, 02 Mar 2007 22:57:51 GMT

Harry wonders if it has been a slow week. It started that way for me but its certainly not now with both

re: Announcing Visual Studio Code Metrics!

John Schroedl — Sat, 03 Mar 2007 03:16:29 GMT

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

How is Maintainability Index calculated?

Chris Woolderink — Sat, 03 Mar 2007 17:32:27 GMT

How do you calculate the Maintainability Index exactly? Only based on Halstead metrics as mentioned before? Or is this based on the formula of Oman (which also includes Cyclomatic Complexity, LOC, Comments)? Or another formula?

I am very curious about this, as I am preparing a Master Thesis research to determine an indicator for maintainability by using .NET code analysis.

New in Orcas - Code Metrics

B# .NET Blog — Sun, 04 Mar 2007 04:14:45 GMT

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

One more goodie with the March CTP

Jeff Beehler's Blog — Sun, 04 Mar 2007 18:11:58 GMT

There really is just so much in the recently released Visual Studio March CTP that it's frankly hard

re: Announcing Visual Studio Code Metrics!

Keith Patrick — Mon, 05 Mar 2007 21:17:53 GMT

"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.

Visual Studio "Orcas" にCode Metrics機能がつく(今回 March 2007 CTPより提供)

米田 Blog ( SQL Server MEMO ) — Mon, 05 Mar 2007 23:44:39 GMT

Visual Studio "Orcas" にCode Metrics機能がつく(今回 March 2007 CTPより提供)

Visual Studio Code Metrics : disponible dès Visual Studio Orcas !

Visual Studio Team System en direct de Microsoft France — Tue, 06 Mar 2007 14:41:12 GMT

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

re: Announcing Visual Studio Code Metrics!

Rob Bryce — Wed, 07 Mar 2007 18:30:40 GMT

Yeah...no code metrics for unmanaged code...there went a day of wasted effort...

re: Announcing Visual Studio Code Metrics!

Scott Rudy — Fri, 09 Mar 2007 06:36:19 GMT

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

Three must-have checks

Steve — Mon, 12 Mar 2007 22:31:47 GMT

Add two checks:

- Dangling property

- Fat body

- Else slope

Dangling property: Check specifically for properties that have Get and set methods that only do the default behavior. We've thousands of non-useful spacefiller lines of code filled with dangling properties based on old coding standards.

Fat Body: Flag loops with a fat body such as a for loop with a body longer than 50 lines.

Else Slope: Flag methods/blocks of code that have large amounts of code in the IF block and 1 or two lines of code in the else block. Especially, flag the methods with multiple levels of unnessary nesting like:

void TooNest(int a)

{

if (a > 0)

{

if (a | 1)

{

if ((a | 3) == 3)

{

(more than 20 lines of code)

}

else

return(a + 1);

}

else

retun(5);

}

else

return(a -1);

return(a);

}

The main criteria is excessive nesting combined with a large ration of (number of lines in if part) / (number of lines in else part)

re: Announcing Visual Studio Code Metrics!

Peter Ritchie — Thu, 15 Mar 2007 18:43:55 GMT

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

re: Announcing Visual Studio Code Metrics!

Aardvark — Mon, 09 Apr 2007 20:48:43 GMT

I have been trying to use "Generate Code Metrics" with my C# project using the March CTP and it tells me "This file contains no managed code.". That is a bit odd because it is all managed code except for some DllImport's in my NativeMethods class. If I use the "Run Code Analysis" option, I do get some Cyclomatic Complexity reports back so some of the analysis is working. Any ideas?

re: Announcing Visual Studio Code Metrics!

David M. Kean — Mon, 09 Apr 2007 20:52:18 GMT

Aardvark,

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

Regards

David

re: Announcing Visual Studio Code Metrics!

Aardvark62 — Mon, 09 Apr 2007 21:57:39 GMT

It has been posted at https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=269597 .

re: Announcing Visual Studio Code Metrics!

Jon — Tue, 17 Apr 2007 19:45:44 GMT

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.

Visual Studio Code Metrics

Tom Lee's blog — Thu, 19 Apr 2007 10:16:05 GMT

Software Metrics 是將軟體設計或規格加以量測與量化的科學，過去在 Visual Studio 2005 Team Edition for Developers 版本中僅提供了靜態程式碼分析

Visual Studio Code Metrics

The Story So Far — Wed, 25 Apr 2007 07:24:47 GMT

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

Rolling up Cyclometric Complexity

Andy Bliven — Thu, 26 Apr 2007 03:52:50 GMT

A more useful measure of the complexity of a class is the average complexity of each method in it. Since this value is normalized it can be used to compare two classes to decide which is more likely to be a maintainence risk, while the simple sum cannot. Alternatively you could define the complexity of the class to be the maximum of the complexity of all its methods, which is similarly useful.

I suppose you've thought of making the metric computation an extension point so I can add my own, perhaps calculated from the primitive measures you've already computed (# methods, # operators, etc.)? You'll never get away with just this fixed set!

I am delighted to see this in Visual Studio, it's a great feature.

Control flow engine, 200?-2007, RIP

I may have joined the wrong side — Sat, 28 Apr 2007 15:49:52 GMT

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

Code Metrics in Orcas

Knowledge, Insight, Action; In that order! — Thu, 03 May 2007 16:53:48 GMT

As if you need another reason to download the CTP / Beta 1 of Orcas: Code Metrics

Visual Studio 'Orcas' Beta 1 Released!

The Visual Studio Code Analysis Team Blog — Sun, 06 May 2007 19:07:35 GMT

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

Code Analysis and Code Metrics - Orcas Team Developer & Suite

The Liquidator — Tue, 05 Jun 2007 07:07:50 GMT

Building quality in ! - The next release of Visual Studio Team developer has some very nice features

Visual Studio Code Metrics : disponible dès Visual Studio Orcas !

Visual Studio Team System — Mon, 09 Jul 2007 10:15:46 GMT

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

New for Visual Studio 2008 - Code Metrics

The Visual Studio Code Analysis Team Blog — Wed, 03 Oct 2007 18:50:42 GMT

While we've already briefly spoken about Code Metrics when we announced it , I thought I would discuss

Code Analysis Features in VS 2008

Noticias externas — Fri, 05 Oct 2007 03:43:06 GMT

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

Code Analysis Features in VS 2008

Somasegar's WebLog — Fri, 05 Oct 2007 20:33:52 GMT

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

advance card cash credit

juegos de poker en espa�ol — Tue, 29 Jan 2008 18:34:18 GMT

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

cash advance detroit

advance america cash first — Sat, 02 Feb 2008 10:39:33 GMT

At cash advance loan texas pay day cash advance payday loan

Todo list

Laumania.net — Fri, 15 Feb 2008 01:36:24 GMT

Todo list

Laumania.net — Fri, 15 Feb 2008 01:36:43 GMT

Todo list

Source Monitor Custom MSBuild Task

markscottjohnson.com — Wed, 12 Nov 2008 01:57:35 GMT

Source Monitor Custom MSBuild Task