title: Best Practices for TFS and MVC projects - deploying changes only
body: <p>I have several websites that I manage for a company and they want me to transition to TFS.  As part of their policy, I can only deploy files that have changed since the last deployment.  I.e.  if a view has changed then it gets deployed, if it has not changed then it not part of the deployment package.  They use automated tools for the deployments.</p>
  
  <p>Currently I use a custom tool I wrote that hooks into my local source provider (Vault Pro) and finds all the changes from a given date and copies those files to a zip file.</p>
  
  <p>How can I accomplish something similar with Team Foundation Server?  </p>