Build ASP.NET apps in Azure Pipelines
Azure Pipelines | TFS 2018 | TFS 2017
In Microsoft Team Foundation Server (TFS) 2018 and previous versions, build and release pipelines are called definitions, service connections are called service endpoints, stages are called environments, and jobs are called phases.
This guidance explains how to build .NET Framework projects. For guidance on .NET Core projects, see this topic.
This guidance applies to TFS version 2017.3 and newer.
This example shows how to build an ASP.NET project. To start, import (into Azure Repos or TFS) or fork (into GitHub) this repo:
The sample app is a Visual Studio solution that has two projects: An ASP.NET Web Application project that targets .NET Framework 4.5, and a Unit Test project.
This scenario works on TFS, but some of the following instructions might not exactly match the version of TFS that you are using. Also, you'll need to set up a self-hosted agent, possibly also installing software. If you are a new user, you might have a better learning experience by trying this procedure out first using a free Azure DevOps organization. Then change the selector in the upper-left corner of this page from Team Foundation Server to Azure DevOps.
After you have the sample code in your own repository, create a pipeline using the instructions in Use the designer and select the ASP.NET Core template. This automatically adds the tasks required to build the code in the sample repository.
Save the pipeline and queue a build to see it in action.
You can use Azure Pipelines to build your .NET Framework projects without needing to set up any infrastructure of your own. The Microsoft-hosted agents in Azure Pipelines have several released versions of Visual Studio pre-installed to help you build your projects. Use the Hosted VS2017 agent pool to build on Visual Studio 2017 or Visual Studio 15.* versions. Use the Hosted agent pool to build using the tools in Visual Studio 2013 or Visual Studio 2015.
To change the agent pool on which to build, select Tasks, then select the Process node, and finally select the Agent pool that you want to use.
You can also use a self-hosted agent to run your builds. This is particularly helpful if you have a large repository and you want to avoid downloading the source code to a fresh machine for every build.
Your builds run on a self-hosted agent. Make sure that you have the necessary version of the Visual Studio installed on the agent.
Build multiple configurations
It is often required to build your app in multiple configurations. The following steps extend the example above to build the app on four configurations: [Debug, x86], [Debug, x64], [Release, x86], [Release, x64].
Click the Variables tab and modify these variables:
Select Tasks and click on the agent job to change the options for the job:
Select Parallel if you have multiple build agents and want to build your configuration/platform pairings in parallel.