mirror of
https://github.com/quamotion/dotnet-packaging.git
synced 2026-02-15 13:46:36 +00:00
Why are so many DLLs in the package? #67
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @aggsol on GitHub (Sep 16, 2019).
Even a small console application is 30MB. Inside are a lot of DLL that are part of the runtime. Is the runtime not a dependency, why also provide those DLLs? Also there is Visual basic DLL and I don't even use that. How can I strip it?
@qmfrederik commented on GitHub (Sep 19, 2019):
The DLLs which are packaged are the result of publishing your application as a framework-independent package using
dotnet publish. It includes the runtime.You are right that it may be easier to declare the runtime as a dependency. This would reduce the size of the application.
There's no built-in support for that right now, but it's something worth considering.
One caveat here would be that your users would be required to add the .NET Core repository for your operating system to their list of repositories before they can install your app, since .NET Core is not packaged by any of the major distro's (that I know of).
@aggsol commented on GitHub (Sep 23, 2019):
Ok. That explains the large packages.