Xileer
Aaah, I was unaware of the bundled native exe. Is there any specific reason for the disproportionate file-size of what is effectively a loader, and is there any way to specify these options manually upon compilation to avoid using it (Or to use a lighter version of it, or have it shared between multiple applications)?
It seems odd that there’s a way to offload this common instruction set to a external location in .NET Framework (mscoree.dll in Windows, something included in Mono on Linux) with no obvious way (That I am aware of) to do so with .NET Core. If you’re already installing a type of “.NET Core Framework” to the operating system (The .NET Core Runtime), should this not include some form of native handling?