3.0 .Net core SDK simplification: VS insertions

[johnbeisner]

We will insert the 3.0 .Net core SDK into 16.3 Visual Studio in a componentized fashion in order to simplify and federate the delivery of servicing updates.

Prototype:
https://devdiv.visualstudio.com/DevDiv/_git/VS/pullrequest/179073

---

Production:

• Arcade supports the publishing to VSFeed
• Repo: aspnet/AspNetCore has adopted Arcade
• Repo: aspnet/AspNetCore manufacturers a NuPkg for each MSI payload - 3.0 SDK
• Repo: aspnet/AspNetCore manufacturers a NuPkg for each MSI payload - 2.1/2.2 Runtime
• Repo: aspnet/AspNetCore publishes the MSI NuPkgs to VSFeed - 3.0 SDK
• Repo: aspnet/AspNetCore publishes the MSI NuPkgs to VSFeed - 2.1/2.2 Runtime
• Repo: dotnet/core-setup has adopted Arcade
• Repo: dotnet/core-setup manufacturers a NuPkg for each MSI payload - 3.0 SDK
• Repo: dotnet/core-setup manufacturers a NuPkg for each MSI payload - 2.1/2.2 Runtime
• Repo: dotnet/core-setup publishes the MSI NuPkgs to VSFeed - 3.0 SDK
• Repo: dotnet/core-setup publishes the MSI NuPkgs to VSFeed - 2.1/2.2 Runtime
• Repo: dotnet/core-SDK manufacturers a NuPkg for each MSI payload - 3.0 SDK
• Repo: dotnet/core-SDK publishes the MSI NuPkgs to VSFeed - 3.0 SDK

---

Product Modifications:

• Self-contained version handling - design
• Self-contained version handling - implementation
• Framework dependent implicit versioning
• Template handling

---

Prototyping:

• Create an drop at VSdrop to support a experimental 3.0 SDK + 2.1/2.2 Runtime insertion
• Create an experimental 3.0 SDK + 2.1/2.2 Runtime insertion into 16.3 VS

---

VS component mapping:

• Map the customer facing VS components for the 3.0 SDK + 2.1/2.2 Runtime insertion
• Map the underlying VS components for the 3.0 SDK + 2.1/2.2 Runtime insertion
• Define the 2.1/2.2 Runtime to be inserted into 16.3 VS with the 3.0 SDK
• Make 2.1/2.2 Runtime component dependent on 3.0 SDK component

---

MSI modification:

• The 'host' MSI owns the PATH modifications
• Each/selected MSIs register versions to the 32-bit registry
• Remove the ability for the current SDK bundle installer to install to a custom location
• Each component MSI should prevent a stand-alone installation

---

Customer communication:

• 3.0 SDK + 2.1/2.2 Runtime customer VS installation methods communications

---

SDK product behavior in VS:

• Uninstalling Visual Studio, should uninstall any .NET Core SDK that it installed