Document shared framework

[Rick-Anderson]

Update 9-18-19:

• Find the right place in this repo for the shared framework doc.
• Ask @natemcmaster to copy paste his blog here. I'll do the conversion.

Update - Deep-dive into .NET Core primitives, part 2: the shared framework looks like it has all the info we need.

The following reference the Microsoft.NETCore.App "shared framework", but it's never defined:

• dotnet command
• .NET Core versioning
• .NET Core Daily Builds -- Servicing and future releases
• Closed issue: ASP.NET Core Shared Framework does a good job of explaining ASP.NET Core Shared Framework, Benefits of a shared framework, Version "train" locking, publishing
• Closed issue:Clarify Shared Framework resolution rules when using FDD Clarify Shared Framework resolution rules when using FDD  #2942

.NET Core distribution packaging comes close, but that's the wrong place to explain the shared framework.

The following pages should be updated to use "shared framework" or at least consistent terminology.

• .NET Core application deployment
• Metapackages - Need to mention this is the shared framework.

dotnet --info lists .NET Core runtimes installed:

Microsoft.AspNetCore.All 2.1.3 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.3 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 2.1.3 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]

.NET Core application deployment (FDD) relies on the presence of a shared system-wide version of .NET Core on the target system.
Is that the shared framework?

Packages, metapackages and frameworks states:
Another set is new frameworks that can be thought of as "package-based frameworks", which establish a new model for defining frameworks. These package-based frameworks are entirely formed and defined as packages, forming a strong relationship between packages and frameworks.

How does that fit in? What is a package-based framework?

[mairaw]

Thanks @Rick-Anderson. @KathleenDollard can you help with this one? Do you see a good place to put such information?

[KathleenDollard]

@terrajobst

[terrajobst]

@richlander would know the details better

[Rick-Anderson]

I would:

• Add it to .NET Core application deployment
• Update the other docs to be consistent
• Cross link as appropriate

[Rick-Anderson]

I'll bet @JRAlexander could knock this out in a couple hours.

[mairaw]

@Rick-Anderson can you help? 😄

[KathleenDollard]

Eeek. It looks like we are using "shared framework" and "framework dependent" pretty much as synonyms. Which is pretty confusing.

@richlander can you weigh in on this (check the use of the two phrases in dotnet command page link above)

[Rick-Anderson]

@KathleenDollard @richlander can we get this scheduled?

[dotnet-bot]

This issue has been closed as part of the issue backlog grooming process outlined in #22351.

That automated process may have closed some issues that should be addressed. If you think this is one of them, reopen it with a comment explaining why. Tag the @dotnet/docs team for visibility.