Skip to content
This repository has been archived by the owner on Apr 11, 2020. It is now read-only.

Incorrect version number in known-issues.md #801

Closed
GregoryOtt opened this issue Oct 4, 2016 · 4 comments
Closed

Incorrect version number in known-issues.md #801

GregoryOtt opened this issue Oct 4, 2016 · 4 comments
Assignees

Comments

@GregoryOtt
Copy link

GregoryOtt commented Oct 4, 2016

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

versioningpb

@GregoryOtt GregoryOtt changed the title Incorrect version number in documentation Incorrect version number in known-issues.md Oct 4, 2016
@markmnl
Copy link

markmnl commented Oct 6, 2016

Question is, where can we get 003131 ???

@balachir
Copy link
Contributor

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.

@shaunluttin
Copy link

shaunluttin commented Oct 19, 2016

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?

@GregoryOtt
Copy link
Author

GregoryOtt commented Oct 20, 2016

@shaunluttin, you can find 003133 at: https://go.microsoft.com/fwlink/?LinkID=827524
See known-issues.md history at: e99bfac

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants