使用 TFS 2012 构建服务器构建 VS2017 项目 [英] Build VS2017 project with TFS 2012 build server

问题描述

我们有一个内部部署的 TFS 2012 服务器和构建服务器.我们正在升级到 VS 和 TFS 2017.目前，有请求设置另一个构建服务器，允许我们从现有的 TFS 服务器构建新的 2017 项目.我创建了一个新的构建服务器并在其上安装了 TFS 2012 构建服务以及 VS2017.我创建了一个新的构建定义，但它无法编译，并且错误显示 2017 年的语法更改等在 2012 年无效的内容.我如何告诉配置它以针对已安装的 VS2017 构建项目?

We have an on-premise TFS 2012 server and build server. We are in the process of upgrading to VS and TFS 2017. At the moment, there is the request to set up another build server that will allow us to build new 2017 projects from the existing TFS server. I create a new build server and installed TFS 2012 build services on it as well as VS2017. I created a new build definition but it fails to compile and errors show things like the syntax changes for 2017 that are invalid in 2012. How do I tell configure this to build the project against the installed VS2017?

推荐答案

旧的 Visual Studio 版本将 msbuild 安装到 C:Program Files (x86)MSBuildin 并且显然RunMSBuild 活动使用 ToolVersion + ToolArchitecture 来计算此路径.

Old Visual Studio versions installed msbuild into C:Program Files (x86)MSBuild<version>in and apparently the RunMSBuild activity used the ToolVersion + the ToolArchitecture to calculate this path.

VS 2017 改为安装 C:Program Files (x86)Microsoft Visual Studio2017EnterpriseMSBuild15.0in 并且 RunMSBuild 无法再计算正确的路径.您不能使用旧的 DefaultTemplate11.1xaml 与 VS2017 集成.

VS 2017 instead installs it C:Program Files (x86)Microsoft Visual Studio2017EnterpriseMSBuild15.0in and the RunMSBuild can't calculate the proper path anymore. You can not use the old DefaultTemplate11.1xaml to integrate with VS2017.

要使其工作，您可以尝试修改 TFSBuildServiceHost.exe.config 并且您必须在构建服务器上安装 VS 2013 或 VS 2015 版本才能使其正常工作.更详细的步骤请按照此链接中的 Jonesy2488's 回答:如何让 VS 2017 与 TFS 2017 XAML 构建一起工作

To make this work, you could try to modify the TFSBuildServiceHost.exe.config and you must have a version of VS 2013 or VS 2015 installed on the build server in order for this to work. More detail step please follow Jonesy2488's answer in this link:How to get VS 2017 working with TFS 2017 XAML Builds

此外，XAML Build 在 TFS 2017 中已弃用，并且不会在 TFS 的下一版本(2018)中可用.VSTS 已经不再支持它们.

Moreover, XAML Build are deprecated in TFS 2017 and will not be available in tge next version of TFS(2018). VSTS already no longer supports them.

我正在寻找托管的 XAML 构建控制器.去哪儿了?

不再支持托管的 XAML 构建控制器.帐户2016 年 4 月或之后创建的用户无权访问它.我们计划从所有帐户中删除托管的 XAML 构建控制器，可能是最快 2017 年 3 月.

The hosted XAML build controller is no longer supported. Accounts created on or after April 2016 do not have access to it. We plan to remove the hosted XAML build controller from all accounts, possibly as soon as March 2017.

来源

既然要升级使用TFS2017.强烈建议您将构建转换为 vNext Build 以获取一些新技术和支持.有关更多信息，请参阅为什么我应该离开 XAML 构建?

Since you are going to upgrade and use TFS2017. Highly recommend you to convert your builds to vNext Build to access some new technology and support. For more please refer Why Should I Leave XAML Builds?

这篇关于使用 TFS 2012 构建服务器构建 VS2017 项目的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！