Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Revisit version numbers and code snippets showing TFMs #2723

Closed
BillWagner opened this issue Jul 23, 2017 · 3 comments · Fixed by #7577
Closed

[Feature] Revisit version numbers and code snippets showing TFMs #2723

BillWagner opened this issue Jul 23, 2017 · 3 comments · Fixed by #7577
Labels
⌚ Not Triaged Not triaged

Comments

@BillWagner
Copy link
Member

BillWagner commented Jul 23, 2017

Many of our samples and code snippets show Target Framework Monikers (TFMs). These need to be updated to the 2.0+ stream of libraries and frameworks.

For example: https://docs.microsoft.com/en-us/dotnet/core/tutorials/using-with-xplat-cli

edit by mairaw: added example

@BillWagner BillWagner added this to the 2017 - Quarter 3 milestone Jul 23, 2017
@mairaw mairaw modified the milestones: September 2017, 2017 - Quarter 3 Sep 5, 2017
@mairaw mairaw added the P1 label Sep 5, 2017
@mairaw mairaw modified the milestones: September 2017, October 2017 Sep 18, 2017
@mairaw mairaw modified the milestones: Sprint 126 (10/21/17 - 11/10/17), 2017 - Quarter 4 Nov 13, 2017
@mairaw mairaw modified the milestones: 2017 - Quarter 4, 2018 - Quarter 1 Jan 8, 2018
@mairaw mairaw modified the milestones: 2018 - Quarter 1, 2018 - Quarter 2 Mar 28, 2018
@dotMorten
Copy link

dotMorten commented Mar 28, 2018

.NET Core SDK is 2.1.101 by now:

image

@mairaw
Copy link
Contributor

mairaw commented Mar 29, 2018

We're aware of that @dotMorten. We're behind on finishing our backlog for 2.0 and we are also planning 2.1 content already, among other releases. This topic will get updated as part of this effort.

@dotMorten
Copy link

@mairaw Not trying to rush you :) Just wanted to make sure this one was handled as part of the issue (the issue is a little vague wrt which ones needs fixing).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
⌚ Not Triaged Not triaged
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants