You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For .NET Core 3.0, we plan to use runtime packs to deliver runtime assets for self-contained publish.
We expect to use "download only" packages to acquire the appropriate runtime pack. This means that the SDK will need to select the correct runtime pack.
We can use a naming convention or a table of packages in the .NET Core SDK to help select the runtime pack. However, we still need to determine which RID to use. This may not be an exact match with the RID used for publish, for example we will want to use the Linux portable (linux-x64) RID for the runtime pack, even if the publish RID is more specific.
To do this, we may want to include the RID graph as part of the SDK, as well as a list of RIDs that there are runtime packs for. Then we can walk the graph to find the best match of available runtime packs to the publish RID.
We should also have some way of opting into a runtime pack for a RID that wasn't in the list of available runtime packs.
The text was updated successfully, but these errors were encountered:
For .NET Core 3.0, we plan to use runtime packs to deliver runtime assets for self-contained publish.
We expect to use "download only" packages to acquire the appropriate runtime pack. This means that the SDK will need to select the correct runtime pack.
We can use a naming convention or a table of packages in the .NET Core SDK to help select the runtime pack. However, we still need to determine which RID to use. This may not be an exact match with the RID used for publish, for example we will want to use the Linux portable (linux-x64) RID for the runtime pack, even if the publish RID is more specific.
To do this, we may want to include the RID graph as part of the SDK, as well as a list of RIDs that there are runtime packs for. Then we can walk the graph to find the best match of available runtime packs to the publish RID.
We should also have some way of opting into a runtime pack for a RID that wasn't in the list of available runtime packs.
The text was updated successfully, but these errors were encountered: