title: Make local TFS build agent to use v14 msbuild tools
body: <p>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.</p>
  
  <p>However, I cannot get builds going since it seems to be looking for v12 tooling - which does not include anything DNX.</p>
  
  <p>So - building the solution gives:
  <img src="https://i.stack.imgur.com/GcdcB.png" alt="The Dnx Runtime package needs to be installed. See output window for more details"></p>
  
  <blockquote>
    <p>The Dnx Runtime package needs to be installed. See output window for
    more details</p>
  </blockquote>
  
  <p>It <em>is</em> 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:</p>
  
  <pre><code>&lt;this:Process.BuildProcessVersion&gt;12.0&lt;/this:Process.BuildProcessVersion&gt;
  </code></pre>
  
  <p>So I switched that to 14, uploaded template, ran build. Then:</p>
  
  <p><img src="https://i.stack.imgur.com/wnUWI.png" alt="The build controller used for this build does not"></p>
  
  <blockquote>
    <p>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.</p>
  </blockquote>
  
  <p>So trying to solve this - got me to this <a href="https://social.msdn.microsoft.com/Forums/vstudio/en-US/20709365-9baf-45ea-a5fd-c0397577895a/could-visual-studio-2013-support-2012-build-controller-machine?forum=tfsbuild" rel="nofollow noreferrer">forum question</a> that states:</p>
  
  <blockquote>
    <p>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 <strong>ToolPath</strong> property to the 2013 version msbuild</p>
  </blockquote>
  
  <p>So - I checked out the template - there is no ToolPath version. There is a ToolVersion property however - which I'll try setting to 14:</p>
  
  <p><img src="https://i.stack.imgur.com/a1Dgl.png" alt="enter image description here"></p>
  
  <p>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?</p>
  
  <p><strong>UPDATE</strong></p>
  
  <p>Seems that the problem is not as much in using the wrong tooling, but more in finding/using the correct DNX runtime <em>while running under a service account</em> ( which the TFS agent is doing ). I've added an issue for the DNX team: <a href="https://github.com/aspnet/dnx/issues/2239" rel="nofollow noreferrer">https://github.com/aspnet/dnx/issues/2239</a> .</p>