Skip to main content

Team Foundation Server 2012: The team project does not support Microsoft Feedback Client.

One of the new features in Team Foundation Server 2012, is the Microsoft Feedback Client; an easy way to allow your users to give feedback on specific functionality of your applications.

This all works fine when you created a new project in TFS 2012, but what if you want to use this feature on an existing project? I f you try to open the Feedback Client for an existing project, it will fail with a similar error message:

The team project ProjectName does not support Microsoft Feedback Client. The team project configuration does not contain valid entry for 'Microsoft.FeedbackRequestCategory'. Contact your Team Foundation Server administrator. For more information, see http://go.microsoft.com/fwlink/?LinkId=223624.

How can we fix this?
  • Open a command prompt
  • Browse to the following location: C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE.
  • Export the categories.xml file:
    • witadmin exportcategories /collection:"collection url" /p:ProjectName /f:c:\categories.xml
  • Update the categories.xml. The exact xml will be different depending on the Process Template. You will have to add at least the Microsoft.FeedbackRequestCategory and Microsoft.FeedbackResponseCategory.

clip_image002

  • Select the appropriate template and click Configure

clip_image004

  • That’s it!

Remark: Depending on the level of customization you did, it’s possible that you have to change some stuff before TFS wants enable these features. For more information have a look at http://msdn.microsoft.com/library/ff432837(VS.110).aspx.

Labels:

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more