title: Do custom check-in policies have to be deployed on the server at all?
body: <p>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.</p>
  
  <p>Is it possible to deploy a custom check-in policy that works in such an environment ?</p>
  
  <p>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.</p>
  
  <p>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.</p>
  
  <p>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)?</p>
  
  <p>Or do I have to build two custom check-in policies, one for the client and one for the server ? Would that even work ?</p>
  
  <p>Or do custom check-in policies only ever exist on the client side ?</p>