TFS 2013和Visual Studio 2017语法

本文介绍了TFS 2013和Visual Studio 2017语法的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

由于Adobe的RoboHelp软件仅作为最高版本使用，因此我们的公司在TFS 2013上陷入困境.我们希望从4.0和VS 2017迁移到.NET 4.6-因此，我们可以使用新的框架功能(如Async/Await)和语言功能(如Tuples).

Our company is stuck on TFS 2013 due to Adobe's RoboHelp software only working with that as a maximum version. We are looking to migrate to .NET 4.6 from 4.0 and VS 2017 - As such we can use new framework featuers (such as Async / Await) and language features (Like Tuples).

不幸的是，当我们使用升级后的内容构建测试项目时，我们的团队构建失败了，我认为这是因为它指向的是4.0 MSBuild.

Unfortunately our team build is failing when building a test project with the upgraded stuff and I assume this is because it's pointing at the 4.0 MSBuild.

我已经安装了VS2017(编译器和.NET 4.6目标包).我已经对该主题进行了一些研究，但是TFS 2013 + VS 2017似乎是一个奇怪的特定组合.但是，我确实发现我需要将ToolsVersion更改为14.0.

I've installed VS2017 (Compiler and .NET 4.6 targeting pack). I have done some research on the topic but TFS 2013 + VS 2017 seems an oddly specific combination. I did however find that I need to change the ToolsVersion to 14.0 which I have done.

然后，MSBuild向我显示我可以拥有的最大ToolsVersion为12.0，这再次使我觉得我正在使用旧的MSBUild.更多研究将我带到我已设置为"C:\ Program Files(x86)\ Microsoft Visual Studio \ 2017 \ Professional \ MSBuild \ 15.0 \ Bin" 的ToolsPath属性.但这仍然给我同样的错误.

MSBuild then shows me that the maximum ToolsVersion I can have is 12.0, which again makes me think I'm using an old MSBUild. More research lead me to the ToolsPath property which I have set to "C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\15.0\Bin". However this still gives me the same error.

我如何才能使VS 2017项目在TFS 2013上构建?我想我需要某种MSBuild路径更改，但是到目前为止我尝试过的路径似乎并不能满足新语法的要求.

How do I go about getting VS 2017 projects to build on TFS 2013? I presume I need some kind of MSBuild path changing but the ones I have tried so far just don't seem to cater for the new syntax.

推荐答案

对于遇到此问题的其他任何人-生成过程模板中可能有多个MSBuild任务，我碰巧有两个，并且一旦更改在第二个任务到达完整的MSBuild路径的工具路径上，我的项目开始构建.

Just for anybody else that comes across this issue - There are potentially multiple MSBuild tasks within the build process template, I happened to have two and as soon as I changed the ToolPath on the second task to the full MSBuild path, my project started to build.