使本地TFS生成代理使用v14 msbuild工具 [英] Make local TFS build agent to use v14 msbuild tools

查看:156
本文介绍了使本地TFS生成代理使用v14 msbuild工具的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有几个ASP.NET vNext应用程序,我希望我的CI服务器也能够构建它们.我的本地计算机和CI服务器都在运行VS2015 RC.然后,我们有了VS Online和一个本地构建控制器-提到的服务器.

I've got a couple of ASP.NET vNext applications and I want my CI server to also be able to build them. Both my local machine and the CI server are running VS2015 RC. Then we've got VS Online and a local build controller - which is the server mentioned.

但是,我无法进行构建,因为它似乎正在寻找v12工具-该工具不包含任何DNX.

However, I cannot get builds going since it seems to be looking for v12 tooling - which does not include anything DNX.

因此-构建解决方案可提供:

So - building the solution gives:

需要安装Dnx Runtime软件包.请参阅输出窗口以了解 更多详情

The Dnx Runtime package needs to be installed. See output window for more details

已安装 -因为它是随VS2015 RC,AFAIK一起提供的.因此,我认为构建模板未使用v14工具.我下载了默认Git模板v12.确实如此:

It is installed - since it came with VS2015 RC, AFAIK. So I thought the build template isn't using v14 tooling. I downloaded the Default Git template v12. And indeed it says:

<this:Process.BuildProcessVersion>12.0</this:Process.BuildProcessVersion>

因此我将其切换为14,上传了模板,然后运行了构建.然后:

So I switched that to 14, uploaded template, ran build. Then:

异常消息:用于此构建的构建控制器没有 支持构建定义使用的模板文件的版本. 模板文件的版本是14.0.最大支持 此构建控制器的版本为12.0.0.0.

Exception Message: The build controller used for this build does not support the version of the template file used by the build definition. The version of the template file is 14.0. The maximum supported version for this build controller is 12.0.0.0.

所以尝试解决这个问题-让我进入

So trying to solve this - got me to this forum question that states:

然后,您需要更改BuildProcessVersion属性,而不是 更改涉及的MSBuild版本.打开构建过程模板,找到运行MSBuild for Project"活动,将 ToolPath 属性更改为2013版本msbuild

Then, instead of changing the BuildProcessVersion property, you need to change the involved MSBuild version. Open the build process template, find the Run MSBuild for Project activity, change the ToolPath property to the 2013 version msbuild

所以-我签出了模板-没有ToolPath版本.但是有一个ToolVersion属性-我将尝试将其设置为14:

So - I checked out the template - there is no ToolPath version. There is a ToolVersion property however - which I'll try setting to 14:

简而言之,我的问题是:如何在安装了VS2015RC的构建服务器上构建ASP.NET vNext应用程序-但是正在使用v12工具进行构建?

In short, my question is: how can I build ASP.NET vNext apps on my build server, that has VS2015RC installed - but is building using v12 tooling?

更新

问题似乎不仅仅在于使用错误的工具,而是在于在服务帐户下运行时找到/使用正确的DNX运行时 (TFS代理正在这样做).我为DNX团队添加了一个问题: https://github.com/aspnet/dnx /issues/2239 .

Seems that the problem is not as much in using the wrong tooling, but more in finding/using the correct DNX runtime while running under a service account ( which the TFS agent is doing ). I've added an issue for the DNX team: https://github.com/aspnet/dnx/issues/2239 .

推荐答案

使用msbuild参数/p:VisualStudioVersion=14.0,可以将其添加到构建定义中.

use msbuild parameter /p:VisualStudioVersion=14.0 ,which can be added in build definition .

这篇关于使本地TFS生成代理使用v14 msbuild工具的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆