search

aspnet / Tooling

Issue tracker and info on Visual Studio tooling for ASP.NET
Other
256 stars 124 forks source link

GetRuntimeToolingPathTarget task can't find global DNX runtime #312

Open JesperTreetop opened 8 years ago

JesperTreetop commented 8 years ago

When running in our TFS build environment, the GetRuntimeToolingPathTarget task in the xproj errors:

2015-12-01T15:32:01.5291905Z        GetRuntimeToolingPathTarget:
2015-12-01T15:32:01.5291905Z          Cannot find DNX runtime dnx-clr-win-x86.1.0.0-rc1-update1 in the folder: C:\Users\TFS_BuildAgent\.dnx\runtimes
2015-12-01T15:32:01.5604421Z ##[error](126,5): Error : The Dnx Runtime package needs to be installed. See output window for more details.

We have installed the RC1 Update 1 Visual Studio package and thus it was installed into C:\ProgramData\Microsoft DNX\runtimes\dnx-clr-win-x86.1.0.0-rc1-update1. A prior build step runs dnvm install latest, which refuses to install DNX into the path the task expects (in the profile) because this global location exists. (A quick reading of the PowerShell script reveals that the Force flag is ignored.)

I worked around this by moving the RC1 Update 1 DNX temporarily from the global location, running our build again to install it into the profile and then placing the global copy back into the global location.

sayedihashimi commented 8 years ago

TFS: 168814 I've added this to our internal TFS, we will reply back here soon.

webtools-bot commented 7 years ago

The GitHub Issue Tracker for the aspnet/Tooling repo is being deprecated in favor of Visual Studio's Report a Problem tool.

If this issue is still a problem with the RTW release of Visual Studio 2017, please report a new issue using the Report a Problem tool. While you can still use .NET Core and ASP.NET Preview tools with Visual Studio 2015, Visual Studio 2017 is now the officially supported tool for developing .NET Core and ASP.NET Core projects.

By using the Report a Problem tool (available in both VS 2017 and VS 2015), you can collect detailed information about the problem, and send it to Microsoft with just a few button clicks. See Visual Studio's Talk to Us page for more details.

Please use the discussion topic here for feedback and questions on the deprecation of this issue tracker. Thanks!