Skip to content
This repository has been archived by the owner on Sep 13, 2022. It is now read-only.

Create targeting pack for .NET Standard #1051

Closed
dsplaisted opened this issue Jan 8, 2019 · 5 comments
Closed

Create targeting pack for .NET Standard #1051

dsplaisted opened this issue Jan 8, 2019 · 5 comments
Assignees

Comments

@dsplaisted
Copy link
Member

For .NET Core 3.0, we expect to separate targeting packs, which contain the assets needed at build time when targeting .NET Core 3.0 (for example, reference assemblies and intellisense documentation) from "runtime packs", which will include the platform-specific runtime components for .NET Core 3. See dotnet/cli#10006, and dotnet/designs#50

We will have targeting pack for each shared framework (.NET Core, ASP.NET Core, and WindowsDesktop), as well as for .NET Standard. This issue tracks the work required a .NET Standard targeting pack. Ideally, we should create targeting packs for both .NET Standard 2.1 and 2.0.

The work required includes:

  • A new NuGet package including the targeting pack assets. This should include the reference assemblies, intellisense documentation, and platform manifest file. The current straw man proposal for the package ID is Microsoft.NETCore.App.Ref
  • Installers for each supported installer format (msi, deb, pkg, and rpm), which lay out the targeting pack files under <DOTNET_ROOT>/packs/<PackageId>/version. These installers will be bundled or depended on by the corresponding .NET Core SDK installers.

Some of the details (such as package layout, names, etc) are still under design and may change slightly.

@wtgodbe wtgodbe self-assigned this Jan 9, 2019
@wtgodbe
Copy link
Member

wtgodbe commented Jan 10, 2019

@dsplaisted @dagood @nguerrera who owns the TargetingPack for .Net Core? @terrajobst and I are trying to figure out what's needed out of Standard to produce what's needed for it (assets/installer etc)

@dsplaisted
Copy link
Member Author

I think @dagood and @ericstj are the right people to start with as far as who will be doing the work to create the .NET Core targeting pack and installers. I don't think much work on that has started though, and it will likely involve working closely with the CLI team to figure out names, file layout, etc.

@dagood
Copy link
Member

dagood commented Jan 11, 2019

That's correct, thanks. I'm getting up to speed on the effort as @rakeshsinghranchi is transferring knowledge to me.

@wtgodbe wtgodbe assigned dagood and unassigned wtgodbe Feb 21, 2019
@terrajobst
Copy link
Member

@dagood @dsplaisted can this be closed now?

@dagood
Copy link
Member

dagood commented May 24, 2019

Sounds good to me. Closing. There are a few outstanding issues, but I don't think they warrant keeping this open:

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