Team Services | TFS 2017 | TFS 2015 | Previous versions (XAML builds)
Here we'll show you how to define your continuous integration (CI) process for your ASP.NET 4 app.
Get set up
For the instructions in this topic, you need an ASP.NET 4 project in Visual Studio.
If you don't yet have an app but want to try this out, then see the Q&A below.
Define your CI build process
Create the build definition
(If you don't see your team project listed on the home page, select Browse.)
- On-premises TFS:
- Visual Studio Team Services:
- On-premises TFS:
- Select the ASP.NET (PREVIEW) template.
- As the repository source, select the team project, repository, and branch.
Enable continuous integration (CI)
On the Triggers tab, enable continuous integration (CI). This tells the system to queue a build whenever someone on your team commits or checks in new code.
Queue and test the build
Save the build definition and queue a new build by selecting the Queue new build command. Once the build is done, click Artifacts and then Explore to see the zip file produced by the build. This is the web deploy package that your release definition will consume to deploy your app.
Deploy your app
After you've run the build, you're ready to create a release definition to deploy your app to:
How do I create an ASP.NET 4 solution?
In Visual Studio, connect to your team project.
On the Team Explorer home page (Keyboard: Ctrl + 0, H), under Solutions, click New.
Select the Web templates section, and then choose the ASP.NET Web Application (.NET Framework) template.
Select MVC from the template list.
Click Change Authentication, select No Authentication, and click OK.
I got a file not found error message. How do I fix it?
All solution files must be checked into the server to run a build. One known cause of missing files is in cases where you populate an empty repo by creating a new project in Visual Studio 2015 Update 3. We recommend that you update your .gitignore file with the latest copy from GitHub: VisualStudio.gitignore.