How can we improve Visual Studio Team Services (VSTS)?

Provide API to generate TFS Warehouse/Code Coverage compatible names for Methods and Types

Currently the Code Coverage details that are loaded into the TFS warehouse use a naming scheme that is not well documented. Nor is there an existing API that can be used to convert from other 'popular' naming schemes or API's to the format Code Coverage uses.

For my TFS Warehouse extension I want to integrate into the existing DimCodeElement dimension, which is fed using the above mentioned formatting for Types and Members. In order to reference the correct CodeElement I need to generate the same strings inside my WarehouseAdapter.


A) Please provide a public PersistenceNameProvider, akin to the existing NameProviders in Microsoft.CodeAnalaysis that we can use to convert from a Microsoft.Cci INode or a System.Reflection based ITypeInfo/IMemberInfo.

Or alternatively create a cross tool naming format which will be used inside the warehouse.

See also:
internal abstract class PersistenceNameProvider : NameProvider
Name: Microsoft.FxCop.Sdk.NameProviders.PersistenceNameProvider
Assembly: Microsoft.VisualStudio.CodeAnalysis, Version=


B) Provide detailed documentation on the formatting used for the different languages supported by CodeCoverage (C#, VB.NET, F#, C++). That way we can implement something like this ourselves.

7 votes
Sign in
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Jesse Houwing shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    We want to build a product that our users love. User Voice provides us a great platform to let any TFS/VSTS user tell us what is important to them. We closely pay attention to the most popular suggestions.

    Too many suggestions in User Voice however will make it hard for you to find the suggestions you want to support. We will regularly archive the suggestions created more than a year ago and has low number of supporters.

    When a suggestion is archived, you can still view them, but you can’t support them anymore. Also Microsoft will not pay attention to these suggestions.

    1 comment

    Comments are closed
    • Jesse Houwing commented  ·   ·  Flag as inappropriate

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

    Feedback and Knowledge Base