Marek Safar
Marek Safar
It looks like you don't have some of the feature switched enabled, see https://github.com/dotnet/runtime/blob/master/docs/workflow/trimming/feature-switches.md. I'm not saying that's all that needs to be done but it's a good start ;-)
@spouliot could you share the binaries?
@spouliot from the log there is still one optimization disabled (--disable-opt unusedtypechecks) which I think is worth investigating why.
The Mono project originally focused on .NET Framework compatibility and it's something that I don't see changing in the future. For Mono plans inside .NET Core setup please read https://devblogs.microsoft.com/dotnet/introducing-net-5/...
Yes, the packages coming from mono/mono will be independent of .NET5+ and .NET5+ MonoVM will live in dotnet/runtime.
Please read the blog it has all the details. There is no plan right now to eliminate MonoVM in .NET5+
The Mono Project is an open-source project and anyway can contribute bugs or new features (for example M1 support landed just recently). As I explained earlier Microsoft's focus is on...
> Windows Forms pull requests are being completely ignored. @Adahel could you point me to specific PRs you would like to merge. The Mono team does not have the capacity...
> I understood it that we will get quality of MS NET5+ libraries with platform versatility of MonoVM That's still the direction we would like to go but it won't...