Currently we're only publishing the framework-independent packages for supported operating systems, which mean that the only external requirements for our packages are that of .NET Core itself.
It could be good for most cases, but is problematic in terms of package size: even if we apply recommendations from #18, the compressed package is still about 14 MiB, which is very significant for an application that only prints its version to the logs and does nothing else. Compressed framework-dependent package may only take 1.8 MiB.
Thus, I suggest we also publish framework-dependent package for people who have an external runtime already installed.
To do that, it's enough to pass --self-contained false to our publish command.
We'll still publish separate packages for all the supported platforms, because the set of native libraries is different, which could create some troubles e.g. if Windows binaries are in macOS app package and require special signing procedure.
Currently we're only publishing the framework-independent packages for supported operating systems, which mean that the only external requirements for our packages are that of .NET Core itself.
It could be good for most cases, but is problematic in terms of package size: even if we apply recommendations from #18, the compressed package is still about 14 MiB, which is very significant for an application that only prints its version to the logs and does nothing else. Compressed framework-dependent package may only take 1.8 MiB.
Thus, I suggest we also publish framework-dependent package for people who have an external runtime already installed.
To do that, it's enough to pass
--self-contained falseto our publish command.We'll still publish separate packages for all the supported platforms, because the set of native libraries is different, which could create some troubles e.g. if Windows binaries are in macOS app package and require special signing procedure.