Tooling: Incorrect version number in known-issues.md

Created on 4 Oct 2016  ·  4Comments  ·  Source: aspnet/Tooling

The version in the documentation (known-issues.md) and the version of the download binary are not the same.

versioningpb

Most helpful comment

In other news, where can we get "version": "1.0.0-preview2-003133"? It seems to be jumping up in the global.json a fair amount: http://stackoverflow.com/questions/39885480/how-to-update-net-core-on-azure-web-app

My colleges have installed .NET Command Line Tools (1.0.0-preview2-003133), whereas I have not been able to find that as a download. This https://www.microsoft.com/net/core#windows for instance installs .NET Command Line Tools (1.0.0-preview2-003131). Was there a widespread problem that lead to the download of 003133 which has now been resolved? Should I be looking for 003113 or instead asking my colleges to rollback to 003131?

All 4 comments

Question is, where can we get 003131 ???

Thanks for reporting this. We had an issue with the fwlinks being used for multiple things. I've updated known-issues.md now with the correct fwlinks for 003131.

In other news, where can we get "version": "1.0.0-preview2-003133"? It seems to be jumping up in the global.json a fair amount: http://stackoverflow.com/questions/39885480/how-to-update-net-core-on-azure-web-app

My colleges have installed .NET Command Line Tools (1.0.0-preview2-003133), whereas I have not been able to find that as a download. This https://www.microsoft.com/net/core#windows for instance installs .NET Command Line Tools (1.0.0-preview2-003131). Was there a widespread problem that lead to the download of 003133 which has now been resolved? Should I be looking for 003113 or instead asking my colleges to rollback to 003131?

Was this page helpful?
0 / 5 - 0 ratings