[Project] .NET Core 2.1 release

[JRAlexander]

This is a meta-issue for the .NET Core 2.1 project.

Comment below to suggest new content, or updates to existing content.

Scenarios:

• Deployment
  • .NET Core Global Tools
• Porting
  • Windows Compatibility Pack Overview
    • Guidance
      • Cross Platform
    • Getting Started and Tutorials
• Platform
  • Building on Windows, cross-targeting to other platforms
  • Dev on Windows / deploy to Linux and reverse
• High Performance
  • Span <T> & Friends Overview- Providing contiguous windows of data without needing to make a copy
    • Working with stack and heap (lifetime and storage)

.NET Core 2.0, updated for .NET Core 2.1 Content Backlog:

Features:

• .NET Core 2.1 Reference API - document APIs

  • Span
  • ReadOnlySpan
  • Memory
  • Pipelines

• .NET Core Global Tools

  • Part 1 .NET Core Global Tools Part 1: Global tools overview, sdk commands, how to use it #4509
  • Part 2 .NET Core Global Tools Part 2: How to create new global tools #6016
  • Part 3 .NET Core Global Tools Part 3: Update extensibility topic #6017

• Patch Management

• Revisit and revise .NET Core SDK Commands [Feature] Revisit and revise .NET Core SDK Commands #4627

• SDK Minor Version Roll-forward [Feature] Runtime and SDK Minor Version Roll-forward #4540

  • Update Version Topic

• Runtime Minor Version Roll-forward

• Windows Compatibility Pack [Feature] Windows Compatibility Pack Updates #4628

  • What's in it?

• [x ] Span<T> [Feature] Span<T> #4400 Overview

  • Memory<T> Create usage guidelines for lifetime management of System.Memory<T> #4823
  • Span UTF-8 parsing overview
  • Buffer best practices
  • Ref struct overview - needs to be expanded (.NET Guide)
    (Refer to 7.2 content)

• Update Deployment Topic

  • Runtime Updates - review RIDs

• Tiered compilation overview

• HttpClient Listener rewritten for performance [Feature] HttpClient Listener rewritten for performance #4541
  - [ ] HttpClient Listener rewritten for performance
  - [ ] Significant changes in 2.1 -> How to get the old version

• System.IO changes #4483

• ARM32 and Alpine support Missing How-To: Installing .NET Core runtime on Raspbian (Raspberry Pi 3) #4663
  - [ ] Alpine-3.6 is now linux-MUSL

Moving from .NET Core 2.0

• Add guidance to use .NET Standard instead of PCL [Feature] Add guidance to use .NET Standard instead of PCL #2724
• CI/CD flow (VSTS) - community contributions for appveyor, .... [Scenario] CI/CD flow (VSTS) and community contributions for appveyor #2714
• Deploying .NET Core console apps into Azure web jobs (for batch jobs) [Scenario] Deploying .NET Core console apps into Azure web jobs (for batch jobs) #2717
• Moving projects to Docker [Scenario] Moving projects to Docker #2702
• https://aka.ms/dotnet-install-templates has bad redirect + No "Install templates docs" https://aka.ms/dotnet-install-templates has bad redirect + No "Install templates docs" #3178
• Create a path for Get Started with .NET Core [Scenario] Create a get started path with .NET Core #2700
• Document how to use cryptography in a cross-plat way Document how to use cryptography in a cross-plat way #761
• Add topic on runtimeconfig.json Add topic on runtimeconfig.json #2645
• Document including runtime specific packages via runtime.json Document including runtime specific packages via runtime.json #1345
• How to migrate from PCL to .NET Standard [Scenario] How to migrate from PCL to .NET Standard #2698
• Document default compiler defines Document default compiler defines  #1483
• Secrets management [Scenario] Secrets management #2718
• Add tutorial to show how to consume .NET Standard libraries with .NET Framework projects, for example [Scenario] Add tutorial to show how to consume .NET Standard libraries with .NET Framework projects, for example #2712
• .NET Framework compatibility [Feature] .NET Framework compatibility #2728
• Migration Guidance for .NET Core 1.x to .NET Core 2.0 Migration Guidance for .NET Core 1.x to .NET Core 2.0 #2732
• Multitargeting topic should include guidance on testing and debugging against a specific target Multitargeting topic should include guidance on testing and debugging against a specific target #1772
• Version binding for .NET Core 2.0 Version binding for .NET Core 2.0 #2880
• Revisit version numbers and code snippets showing TFMs [Feature] Revisit version numbers and code snippets showing TFMs #2723

Announcements:

• What's new in .NET Core 2.1 What's new in .NET Core 2.1 #4933
  • Build-time Performance

Other:

• Added note about SDK 2.1 added note about sdk 2.1 #4385 - Clarifying versioning.
• SDK and Runtime Versioning Update .NET Core versioning topic for 2.1 #4352
• New and Improved Docker Images
• Review and revise Prerequisite articles
• Review topics that have ms.custom: "updateeachrelease" (that are not framework specific) such as https://docs.microsoft.com/en-us/dotnet/standard/frameworks
• Remove SignalR from list of technologies not available on ,NET Core (https://docs.microsoft.com/en-us/dotnet/standard/choosing-core-framework-server)
• Content Move - Network programming and ADO.NET to .NET Guide instead of Fx.
• .NET Core 2.1 SDK - what language versions are included in each release?
• Need to determine which .NET Core SDK has which C# version enabled Need to determine which .NET Core SDK has which C# version enabled #4154
• Document System.Hashcode in .NET Core 2.1 API Document System.Hashcode in .NET Core 2.1 API #4936
  edit by @mairaw: added new work items

[dasMulli]

Is there a plan to start an area or branch with preview docs for 2.1 already? Some of the work items may be helpful during the preview timeframe (e.g. global tools, versioning, roll-forward) to help (and even make) ppl try out preview features.

[mairaw]

Hi @dasMulli, some we might start working on that soon like global tools. I think we won’t create a different folder/area for 2.1. We’ll add things as they make sense in the TOC. We’ll go through a prioritization exercise for our 2.1 work vs. remaining 2.0 work as well to see what to work on next.

[ChrisMaddock]

I've just come across System.HashCode - which is new in .NET Core 2.1, but lacking documentation currently. Is this tracked somewhere else? It didn't seem to fit any of the existing points.

https://docs.microsoft.com/en-gb/dotnet/api/system.hashcode?view=netcore-2.1&viewFallbackFrom=netstandard-2.0

[mairaw]

You can create a new issue for that @ChrisMaddock. There are quite a few undocumented APIs for the .NET reference and an ongoing project for filling those gaps: https://github.com/dotnet/docs/projects/15.

We also created an internal report to discover all those. But the ones captured here were the ones considered high-priority for the release. Makes sense?

[ChrisMaddock]

Thanks @mairaw - I've moved it here: #4936

[JRAlexander]

Thanks, @ChrisMaddock, I've added it in this issue above, and also in the .NET Core 2.1 project.