Source versioning and continuous integration with Git and TFS

In the Deploying a Website recipe, we saw how to deploy a Website directly through FTP or Web Deploy. Those strategies are very fast and effective; however, they are not always suitable in complex scenarios because of the following reasons:

• Developers cannot have direct access to the final endpoint or they should not even know what the final endpoint is
• Automated builds/tests should be performed after each release and check in, centrally controlled on a specified server

These two scenarios involve new actors while deploying Websites; in addition to the Developer and the Website, now there is also the source repository. In this recipe, we see how to invert the process:

• From:
  • Developer upgrades/updates the Website directly
• To:
  • Developer saves his or her code somewhere
  • The Website takes that code and deploys it

This inversion of control makes the publishing process an administrative task by establishing a link between the Website and the...