Home/ Questions/Q 306227
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-12T07:26:51+00:00

I’m asking this question because I haven’t seen it documented anywhere. We are using

  • 0

I’m asking this question because I haven’t seen it documented anywhere.
We are using a combination of Team Foundation Server 2008 and Team Explorer 2005.

Is it possible to deploy a custom check-in policy that works in such an environment ?

Obviously, the custom check-in policy contains some code that must run on the client-side (in order to display help, etc.). So it should use the Microsoft.TeamFoundation.VersionControl.Client assembly that comes with Team Explorer 2005.

But, my sense tells me that, in order to be effective, a check-in policy should be enforced on the server itself (for example, to support checking-in changes from the command-line or using the raw Web Services API). So, there, it would have to run against the Microsoft.TeamFoundation.VersionControl.Client that comes with Team Foundation Server 2008.

So, is it possible to build a single custom check-in policy that takes the most recent version the Microsoft.TeamFoundation.VersionControl.Client assembly (2005 on the client and 2008 on the server)?

Or do I have to build two custom check-in policies, one for the client and one for the server ? Would that even work ?

Or do custom check-in policies only ever exist on the client side ?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The custom check-in policies only exist at client-side, and will only be evaluated client-side. If the DLL is missing on the client computer, TFS will complain, but provide a dialog that allows the user to override the error and check in anyways.

    • 0