Packs vs Shared libraries: More information is welcome

[MarcioAB]

For example: Why the project default libraries (as in assembly load context libraries) points to libraries in shared directory but the project framework (as in project dependencies) points to pack directory ? Why libraries in pack directory have xml documentation and libraries in shared directory don't. Why they have different sizes ?

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 1ce2ad2f-c2fb-b15a-fb97-75417a1b51e8
• Version Independent ID: 40eec307-4ff8-e68f-c8a7-ead32cccf776
• Content: .NET Core distribution packaging - .NET Core
• Content Source: docs/core/build/distribution-packaging.md
• Product: dotnet-core
• GitHub Login: @tmds
• Microsoft Alias: mairaw

[tmds]

https://docs.microsoft.com/en-us/dotnet/core/build/distribution-packaging is for explaining to Linux maintainers how they can package .NET Core.
I think this isn't the right document to explain the design.

cc @dagood @nguerrera

[dagood]

I agree this page isn't where we should describe shared frameworks (runtimes) vs. framework packs. dotnet/designs/accepted/install-locations.md and dotnet/designs#50 are the only semi-official places I can think of where I've seen these documented.

(Once we do have it documented (or if someone finds some docs), I think it would be good to link to that from this distro packaging page so that maintainers can understand what they're putting together, though.)

[dotnet-bot]

This issue has been closed as part of the issue backlog grooming process outlined in #22351.

That automated process may have closed some issues that should be addressed. If you think this is one of them, reopen it with a comment explaining why. Tag the @dotnet/docs team for visibility.