How to fix DNX/DNVM in Visual Studio 2015?

Question

Today I installed VS 2015 on Windows 7 x64. Mainly to test new .Net Core features and etc. And for test I created new C# "Console Application (Package)" solution and got this message:

DNX SDK version 'dnx-clr-win-x86.1.0.0-beta5' failed to install. The solution will use DNX SDK version ‘dnx-clr-win-x86.1.0.0-beta5’ for this session.

I can't compile and debug project. Also, when I have opened debug tab in project properties then VS crashed.

DNVM output when I opened solution:

Invoke-Command : The term 'x86' is not recognized as the name of a cmdlet, func
tion, script file, or operable program. Check the spelling of the name, or if a
 path was included, verify that the path is correct and try again.
C:\Program Files\Microsoft DNX\Dnvm\dnvm.ps1:1451 ????:27
+             Invoke-Command <<<<  ([ScriptBlock]::Create("dnvm-$cmd $cmdargs")
)
    + CategoryInfo          : ObjectNotFound: (x86:String) [Invoke-Command], C 
   ommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException,Microsoft.PowerShell.Co 
   mmands.InvokeCommandCommand

Invoke-Command : The term 'x86' is not recognized as the name of a cmdlet, func
tion, script file, or operable program. Check the spelling of the name, or if a
 path was included, verify that the path is correct and try again.
C:\Program Files\Microsoft DNX\Dnvm\dnvm.ps1:1451 ????:27
+             Invoke-Command <<<<  ([ScriptBlock]::Create("dnvm-$cmd $cmdargs")
)
    + CategoryInfo          : ObjectNotFound: (x86:String) [Invoke-Command], C 
   ommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException,Microsoft.PowerShell.Co 
   mmands.InvokeCommandCommand

Invoke-Command : The term 'x86' is not recognized as the name of a cmdlet, func
tion, script file, or operable program. Check the spelling of the name, or if a
 path was included, verify that the path is correct and try again.
C:\Program Files\Microsoft DNX\Dnvm\dnvm.ps1:1451 ????:27
+             Invoke-Command <<<<  ([ScriptBlock]::Create("dnvm-$cmd $cmdargs")
)
    + CategoryInfo          : ObjectNotFound: (x86:String) [Invoke-Command], C 
   ommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException,Microsoft.PowerShell.Co 
   mmands.InvokeCommandCommand

Any ideas how to fix it?

Also, I have previously installed VS 2015 Preview and DNX/DNVM separately. But I think, I completely removed it before VS 2015 installation. Could this somehow affects current VS installation?

Answer 1

Install the latest version by opening a console and running:

dnvm upgrade

If you reopen VS you should be able to compile.

If this doesn't work, try deleting the C:\Users\username\.dnx folder. Reopen VS and it will recreate the .dnx folder in the same location with only 2 scripts: bin\dnvm.cmd and bin\dnvm.ps1 Note: This would delete all already installed runtimes.

Rerun dnvm upgrade and check under the project properties if the Solution DNX SDK Version you have matches an installed one.

Answer 2

My version of powershell was 3.0, then I:

1. Install powershell v.4 from:

https://www.microsoft.com/en-us/download/details.aspx?id=40855

2. Reboot windows

This solve my problem.

Answer 3

I could fix it by this way: In Developer Command prompt for 2015 enter this command

dnvm install 1.0.0-beta5

sure this way will can fix your issue.!

Answer 4

If anyone have problems with dnx not available in Visual Studio 2015 while watching some bit outdated tutorials ( like me ) check below link

The RC2 release of .NET Core and ASP.NET Core 1.0 moved from DNX to the .NET Core CLI.

In the table on the linked page you will the mapping between the DNX/DNU commands and their CLI counterparts. for example:

dnx run becomes dotnet run

Answer 5

I had a similar problem earlier today, and the way in which I managed to solve it after reading the comments in this page was very straight forward.

First of all I have to say that I already had PowerShell 3.0 installed (not having it installed seems to be the main source of this problem for most people) and yet I still was having this same issue.

So instead of having to edit and modifying the powershell scripts involved in order to make them work with paths with whitespaces, etc as suggested, I just simply did as follows (much simpler):

1.- Go to "C:\Program Files (x86)\Microsoft Web Tools\DNX" in Windows explorer and "copy" all its content (basically all the packages and their sub-folders)

2.- "Paste" all that content into a path with no blank spaces. I used "C:\Temp\"

3.- Run the following commands on the command line (notice there are no blank spaces now in the path locations indicated)

dnvm update-self
dnvm install "C:\Temp\dnx-clr-win-x64.1.0.0-beta5.nupkg"
dnvm install "C:\Temp\dnx-coreclr-win-x64.1.0.0-beta5.nupkg"
dnvm list

4.- Open your Visual Studio solution now and on your Project -> Properties -> Application tab, in there you can now specify the version of the DNX SDK that you want to use from those of which you have now available

5.- Re-build your solution and it should now be all fine

Nice one!

Answer 6

try

dnvm update-self
dnvm install -u  -r clr  -OS win  -a x86  beta5 -ngen 

important are the -u parameter (unstable) and the beta5 version string.