TFS2017 Continuous Integration Build

TFS2017 has been released for several months, after a few days of deployment and trial, TFS2017 's functional changes are really big. In particular, in terms of building changes, the XAML versioning controllers and proxies have been declared deprecated in the Product's wizard, and it is recommended to upgrade the previous production upgrades in 13 and 15 to the new production system, but at the same time, it is estimated that the reason for the retention of forward compatibility is the same as the XAML configuration pattern.

For the first time in the premise environment, the use of TFS2017 construction, or experienced some twists and turns, but after more than 10 attempts or the final construction success, small excitement also followed. Here's the whole process from preparing a project, creating a build definition to an integration build.

1, create a typical ASP. NET MVC project, and join the VC library.

Figure 1 Web project created based on vs built-in project template

2, create a build definition, where a few pits, to be properly configured, otherwise the construction is unsuccessful.

Figure 2 Specifying the build solution file

Figure 3 Configuring a shared folder as the publishing path

Figure 4 Specifying the publishing path

3, trigger build, automatically trigger when code is checked in, or trigger manually

Figure 5 Manually triggering the build

4, build results

Figure 6 Build results

TFS2017 Continuous Integration Build