Broken in Vs2010 SP1

I also had problems with VS 2010 SP1 and NET 4.0. The reason for the problem is that a mixture of assemblies is taken from GAC and VisualStudio folder with an invalid combination. To fix this, I did the following steps to force the custom control to use the assemblies I wanted: - change Project to Build for .NET 4.0 Full/Client Profile - remove all references to TFS Assemblies from project and Build once (errors will occur) - collect these assemblies from Visual Studio Program Folder and add them directly to the WitCustomControls Project: C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies\Microsoft.TeamFoundation.WorkItemTracking.Controls.dll C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\ReferenceAssemblies\v2.0\Microsoft.TeamFoundation.Client.dll C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\ReferenceAssemblies\v2.0\Microsoft.TeamFoundation.WorkItemTracking.Client C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\ReferenceAssemblies\v2.0\Microsoft.TeamFoundation.Common.dll - add direct references to the assemblies with Properties: local copy = true; specific version= true; - now the assemblies will belong to the output - deploy the whole build into the CustomControl folder C:\ProgramData\Microsoft\Team Foundation\Work Item Tracking\Custom Controls\10.0 - restart visual studio and open your workitem - to deploy the custom controls to other workstations simply copy the folder The attached screenshot shows my CustomControlsFolder. Jan

I am running into this same issue. Does anyone have any more information? Is there a solution yet? Thanks, Troy

Seems like the conflict is with the TFS 2010 powertools March 2011