This course will take you from beginning to end, setting up a continuous deployment pipeline for an ASP.NET application. You'll learn: how to configure a destination server to accept remote deployments using Web Deploy, how to leverage TFBuild's extensibility to automatically deploy your ASP.NET application and how to do all this in an automated fashion. You'll finish up by customizing a build template to provide a seamless user experience.
David is a software developer with a back ground in IT systems administration. When he’s not learning something new about technology, or speaking about technology, he enjoys billiards and watching/attending motocross races.
Continuous Deployment with Team Foundation Server 2010 Hello. This is David Batten and welcome back to Continuous Deployment with Team Foundation Server 2010. In this module, we will be talking about the systems and configurations necessary to enable automated deployment on a Windows server. We'll start by talking about the features and services. Since we will be deploying a web application to IIS 7, we'll need to visit the server and make sure that the following services are enabled. IIS Management Scripts and Tools gives us the ability to script deployment activities and the Management Service gives the ability to expose IIS 7 to incoming deployments across the wire. The Web Deployment Framework, or Web Deploy, is a tool that we will download and install. And the three features that you see here give us the ability to automate deployments with non-administrator accounts. Web Deploy also includes a remote agent service feature that we won't be using for our examples. Although remote agent service allows you to do automated deployments, it acquires administrative permissions to do its jobs. So, in the interest of security, we won't be using it. And instead we will be using the IIS 7 Deployment Handler.