Triaging in #9
Duplicate. Will continue monitoring http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/2047315-merge-by-workitem.
This is now available at Visual Studio Code Metrics PowerTool 11.0 → http://www.microsoft.com/en-us/download/details.aspx?id=38196
Again, same request, but now for 2013 and please fix the bugs...
And while you're at it, this bug also warrants a little fix :)
Please include the Test Impact Analysis/ Code Coverage compatible Business Key/Surrogate key (which looks like a base64 encoded binary identifier of the method signature) as part of the metrics report as well. That way it is a lot easier to include Code Metrics as part of the reports in the future.
Looking at the decompiled sources I can confirm that it's explicitly using the CurrentCulture instead of InvariantCulture.
Would it be possible to open up the MeticsCalculator class, even of it only exposes the calculated results?
Another thing I noticed is that is uses the User's culture to format the numbers inside the XML as far as I can tell (or at least it's using my Dutch thousands separator in Lines of Code)
<Metric Name="MaintainabilityIndex" Value="90" />
<Metric Name="CyclomaticComplexity" Value="7.009" />
<Metric Name="ClassCoupling" Value="363" />
<Metric Name="DepthOfInheritance" Value="6" />
<Metric Name="LinesOfCode" Value="11.674" />
I would expect it to use an invariant culture as this file is meant for machine parsing.
Additional feature requests for the tool:
- xslt shipping with it which transforms the report to an excel or html report
- a msbuild tool plus matching targets file (I have one on hand should anybody want to have it)
Posted by a Visual Studio ALM RangerJesse Houwing shared this idea and gave it 3 votes ·
The solution idea did not meet triage scope and priorities and should be triaged by the ALM community, rejected or launched as a community solution.
Might as well add how to create an installer for your adapter as well. Turns out that creating a simple x86 installer that automatically installs into the correct Plugins folder for your warehouse adapter is not possible. Need to create separate x86 and x64 installers.
Creating a TFS Report repository was proposed multiple times by multiple people during the review of this project proposal. It looks like someone went ahead and created a codeplex project to do just that. Would be nice to incorporate/use that:
I'd also like to add some guidance on how to collect you data. I've ended up creating both an MsBuild Task (to gather statistics) and a Build Activity (to store the statistics in the build details). That was a lot easier to do than sticking all the functionality into the build activity, as you don't have information about external references, project outputs etc at hand. Plus it's easier to override settings on a per-project basis if needed.
If not a full DVCS, I'd love it if it were possible to take my solution offline into a local "TFS Basic instance" with just Source control and read only work items. Then upon return I'd like to be able to commit my changes to the central TFS either by "Latest local version" all at once or by changeset.
It'd be even better if I could pre-associate my work items with my local changsets.
I wouldn't need to be able to take an editable work item store offline, but I'd love to be able to query the work items without the need to be connected to the central TFS.
Same also applies to the new review feature, currently you can't perform a review while offline, nor can you request a review while offline.
Improving the querability of Work items and TFS artifacts is something we’re looking into.