TFS Version Control Tasks

TFS Version Control Tasks

• Doug Haacke

  You are correct that there is no custom task for checking in or checking out files. Out of curiosity - why would you want to do this during the build process

  -Aaron

  
  
  

• Peter67

  While I'm not the initial poster I can speak for why I need these tasks.

  To utilize TFS as a Publication point build results. These can be libraries are used in multiple dependent Solutions. Other situations, we have automated build processes to build XML files that are used in build processes. I want these files versioned and managed in Source Control not on shared drive spaces.

  
  

• SkyPhy

  Also not the original poster, but my team uses a Team Build for continuous integration. We also use code generation (lots!). To make sure we are building and testing the code from the code generation templates, we checkout, codegen, checkin, relabel and compile our projects. This allows us to promote a version of code to the Enterprise build that doesn't require code generation at that level as they can Get by label.

  We use are large amount of code generation, so ensuring that all generated code, across the entire project (many assemblies) are updated when a template changes is very important to us. Since there are so many to manage, it is possible for a developer to forget to regen a file after a template change. This solves that problem.

  I have written a custom task which fires a console app that does the checkout, codegen, checkin and label for us during our builds.

  
  
  
• TFS Version Control Tasks