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 expect to separate targeting packs, which contain the assets needed at build time when targeting .NET Core 3.0 from "runtime packs", which will include the platform-specific runtime components for .NET Core 3 which are deployed with self-contained apps.
This issue tracks the work required in order to support runtime packs. This includes:
While acquisition is important, I believe that deleting / cleaning installed runtime packs is also important:
Clean outdated versions (e.g. 2.0.5 and 2.0.6 are installed: 2.0.5 is no longer needed)
Could be done automatically on acquisition of 2.0.6 for the same RID
Clean by RID (inclusive or exclusive)
If an SDK installer adds a pack (e.g. win-x64 installer installs win-x64 runtime pack), uninstalling the SDK version should remove the runtime pack as well (ref-counted)
Another important aspect is:
Where are the runtime packs installed? User or machine wide directory?
Can these be consumed via dotnet publish --runtime-packs ~/netcore-runtime-packs?
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 from "runtime packs", which will include the platform-specific runtime components for .NET Core 3 which are deployed with self-contained apps.
This issue tracks the work required in order to support runtime packs. This includes:
dotnet runtime-pack install Microsoft.NETCore.App -version 2.0.6 -rid linux-x64
The text was updated successfully, but these errors were encountered: