I have custom check-in policies deploying via VSIX. Now I\'m trying to use them in Visual Studio 2013.
What I did: I opened my policies in VS 2013.
I had the same problem, a custom policy working on VS 2008/2010 don't install correctly in vs2013. Finally I opened the custom policy project in VS 2013, then I readded Microsoft.TeamFoundation.VersionControl.Client reference and compile it. Now it works and recognize as the same policy that VS2010.
As the Original Poster has posted, the version of .NET and of the referenced Client Object Model:
8.0.0.0
assemblies and your project must be an AnyCPU .NET 2.0 project.9.0.0.0
assemblies and your project must be an AnyCPU .NET 3.0 project.10.0.0.0
assemblies and your project must be an AnyCPU .NET 4.0 project.11.0.0.0
assemblies and your project must be an AnyCPU .NET 4.0 project.12.0.0.0
assemblies and your project must be an AnyCPU .NET 4.5 project.14.0.0.0
assemblies and your project must be an AnyCPU .NET 4.6 project.If you have multiple versions of Visual Studio installed, you need to deploy the assembly multiple times, once for each version of Visual Studio. These assemblies must have the same AssemblyName
and the same AssemblyVersion
and be signed with the same strong name.
The policies must each be registered in the registry under the following keys:
HKEY_LOCAL_MACHINE\Software\Microsoft\VisualStudio\{VisualStudioVersion}\TeamFoundation\SourceControl\Checkin Policies
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\{VisualStudioVersion}\TeamFoundation\SourceControl\Checkin Policies
(64 bit OS only)HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\{VisualStudioVersion}_Config\TeamFoundation\SourceControl\Checkin Policies
(should be added automatically by running devenv /setup
)A more extensive walkthrough can be found on my blog.