Keep in mind that it's just one option. If you want, you can still deploy your app separately from the .Net runtime.

Also, to keep the size at least somewhat in check, unused parts of the base library are not included in the single-file mode.

Keeping in mind it's also a double edge sword. TLS deprecations alone will ensure your app will die after a few years if it doesn't run on an up-to-date CLR.

30 years ago we used DOS and DLL Hell was a completely unknown concept. We did have to deal with himem.sys though.

"Insert floppy disk 435 of 880 and press [Enter] when ready..."

You create a single binary which has the runtime and dependencies self contained within.

You of course have to choose your target platform for this as it makes .exes for Windows, ELFs for Linux, etc.

If you want you can still choose to distribute IL DLLs and users then use their already installed dotnet on their machine to run them.

You create one binary per OS.

Something like 60MB if the application is not trimmed. Closer to 10MB if the application can be trimmed.

In my case about 60MB