search

aspnet / dnvm

OBSOLETE - see readme
Other
174 stars 61 forks source link

Trouble switching runtime with alias #483

Closed TJSoftware closed 8 years ago

TJSoftware commented 8 years ago

You can see in the attached screenshot that I first created an alias. I then listed to see where Active was. I attempted to use the command dnvm use <alias> to switch the active runtime. I ran dnvm list and the active had not been changed. To verify that I could change the active I used the full runtime version, runtime, and architecture. I ran another list after that to confirm and the active runtime was updated.

aliasissuecleaned

BrennanConroy commented 8 years ago

What version of dnvm

TJSoftware commented 8 years ago

.NET Version Manager v1.0.0-beta5-10384

BrennanConroy commented 8 years ago

That is a very old version, this bug has already been fixed

TJSoftware commented 8 years ago

Ahh, thanks for letting me know. I will upgrade, I must have got confused on what VM I was on.

TJSoftware commented 8 years ago

I ran a dnvm upgrade but the version was the same. I also tried dnvm upgrade -u. Is this the incorrect command to upgrade the dnvm?

BrennanConroy commented 8 years ago

dnvm update-self

TJSoftware commented 8 years ago

Updating dnvm from https://raw.githubusercontent.com/aspnet/Home/dev/dnvm.ps1 dnvm-update-self : Exception calling "DownloadFile" with "2" argument(s): "An exception occurred during a WebClient request." At C:\Program Files\Microsoft DNX\Dnvm\dnvm.ps1:1453 char:13

BrennanConroy commented 8 years ago

You probably have one of the bad versions where update-self was broken, you'll have to manually update it from the Home repo

TJSoftware commented 8 years ago

Ok, thanks for the fast responses. I will get the latest.

TJSoftware commented 8 years ago

P.S. When in doubt turn it off and on. I closed the command prompt and reopened. At that point the dnvm update-self worked. My current version is .NET Version Manager v1.0.0-rc1-15535.

TJSoftware commented 8 years ago

I was also able to confirm that this is fixed in the latest version.

cda-1 commented 8 years ago

For any googlers, try in an admin command prompt. That fixed the issue for me.

TJSoftware commented 8 years ago

@cda-1 I also found that while on beta5 you need to upgrade to beta8 before this works. Here is a link to upgrade to beta8. https://www.microsoft.com/en-us/download/confirmation.aspx?id=49442