NET 5, we are taking this further, and cracking open the assemblies, and removing the types and members that are not used by the application, further reducing the size.
It will then only package those assemblies into the app, thereby reducing the size of the application. Optionally during the publish process, a trim phase occurs which does an exhaustive walk of the code paths identifying the assemblies that are used by the code. It is also sometimes called the “assembly linker”. We first made assembly trimming available as part of. To resolve the size problem, we introduced an option to trim unused assemblies as part of publishing self-contained applications. The downside is the size – it pulls along a complete copy of the runtime & framework.
From anĪpplication developer perspective, this means that you know exactly which version of the runtime is being used, and the installation/setup is easier. It doesn’t depend on having the framework separately installed. NET Core supports self-contained deployment – everything needed to run the application is bundled together.
0 kommentar(er)
