-
Notifications
You must be signed in to change notification settings - Fork 424
Create targeting pack for .NET Standard #1051
Comments
@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) |
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. |
That's correct, thanks. I'm getting up to speed on the effort as @rakeshsinghranchi is transferring knowledge to me. |
@dagood @dsplaisted can this be closed now? |
Sounds good to me. Closing. There are a few outstanding issues, but I don't think they warrant keeping this open:
|
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:
Microsoft.NETCore.App.Ref
<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.
The text was updated successfully, but these errors were encountered: