Hold down [ALT] each lens will show a number (2 for references for example). This will directly open that lens.
[ALT]+[->] and [ALT]+[<-] allows you to navigate between lenses
Once a lens is opened you can use arrow-up/down to navigate the lens content.
10 votes2 comments · Visual Studio » Team Foundation Server & Visual Studio Online · Flag idea as inappropriate… · Admin →
The standard TFS proxy server works against Team Foundation Service / Visual Studio Online.
12 votes7 comments · Visual Studio » Team Foundation Server & Visual Studio Online · Flag idea as inappropriate… · Admin →
In Visual Studio Online and TFS 2013 Git commits can be linked to work items. From the Pending Changes window, work items can be added using the UI features or by adding a mention to the commit comment in the form of “#ID” where ID is the work item ID.
TFS Program Manager
This is part of Visual Studio Online and TFS 2013. The feature is enabled by default, use the following format #workitemnumber See also: http://www.codewrecks.com/blog/index.php/2013/01/31/associate-work-items-to-check-in-in-a-tf-service-git-enabled-repository/
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 Ranger
1 vote2 comments · Visual Studio » Team Foundation Server & Visual Studio Online · Flag idea as inappropriate… · Admin →
This should be fairly simple to implement using a MsBuild target and adding a list of disallowed words to the msbuild.exe command line. How do you envision these 'bad words' to be defined? Is it a short list of strings? Or does their location inside the source make them more or less important? (Parsing the sources and ensuring these only occur inside the comments is more work ;).
Check out Mono-Andoid, does exactly what you're looking for:
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.
7 votes1 comment · Visual Studio » Visual Studio Test and Lab Management · Flag idea as inappropriate… · Admin →
Not included in ALM Rangers triage #3 and handing back to PG.
Aside from the warehouse specific naming system, it looks like the Business Key / Surrogate Key generated by Test Impact analysis and Code Coverage is a base64 encoded binary identifier of the method signature. It would be very helpful if we could generate that too :).
61 votes2 comments · Visual Studio » Team Foundation Server & Visual Studio Online · Flag idea as inappropriate… · Admin →
See the TEK WorkItem Toolkit for a addon to Visual Studio that provides such functionality for TFS 2010 and soon also for 2012. http://visualstudiogallery.msdn.microsoft.com/1397f185-7f49-49c8-ad80-e45fc9dbbfe9
Installers will introduce maintenance and especially quality process requirements that will impact the ability for ALM Rangers to respond quickly to adoption blockers. We will decline this idea for all solutions, but consider for selected solutions that can absorb the additional cost.
For books I prefer epub and/or mobi as well, so that I can read it on my e-reader. It also allows us to publish them via Amazon (even for free). and other ebook vendors.
I also like integration of the guidance into the MSDN library so that it comes up with helpful details when I search or press F1. This is something the installer can do.
I like PDF mostly for printing since it doesn't flow to fit the screen of my tablet nor ereader.
As for powershell scripts, tools, samples and other bits including MSDN help integration, I love that to be part of an installer (or the Web Platform Installer or Nuget).
I have a build task plus targets file that does this. Would you care to give it a private testdrive?
Also improve wording to clearly indicate which (sour, target or both) will be updated as part of a sync, migration or move. The current documentation uses Move, Transfer, Migrate which tend to indicate the removal from one and creation in the other system. Which often isn't the case, but it caused my to triple check my settings on multiple occasions and doing dry runs just to be sure.
Duplicate. Will continue monitoring http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/2047315-merge-by-workitem.Jesse Houwing supported this idea ·