[Feature Request]: .NET 6 Target with Trimming

[ds5678]

A .NET 6 target for the decompiler project with trimming would allow this to be used in NativeAOT apps.

Issues to be dealt with:

• A bunch of Linq substitutes need excluded on .NET 6 with preprocessor directives.
• ResXResourceWriter.cs uses TypeDescriptor.GetConverter and BinaryFormatter.Serialize.
• UniversalAssemblyResolver.cs calls Type.GetType("Mono.Runtime") which I think can be safely excluded with a preprocessor directive on .NET 6.
• 6a6e82c added ReferenceAssemblyAnnotator which breaks when targeting multiple frameworks [Bug]: Breaks with multiple framework targets tunnelvisionlabs/ReferenceAssemblyAnnotator#92

[christophwille]

What sort of app using a decompiler would be using NativeAOT?

[siegfriedpammer]

ReferenceAssemblyAnnotator is not going to be removed unless Microsoft adds nullable attributes to netstandard2.0 out of the box. Too many customers depend on netstandard2.0, so we cannot upgrade and of course adding NRT to the decompiler is also a must at this point.

Thank you for your understanding!

[ds5678]

What sort of app using a decompiler would be using NativeAOT?

I have a game recovery project where performance is very important. NativeAOT would help with that.

[ds5678]

ReferenceAssemblyAnnotator is not going to be removed unless Microsoft adds nullable attributes to netstandard2.0 out of the box. Too many customers depend on netstandard2.0, so we cannot upgrade and of course adding NRT to the decompiler is also a must at this point.

Thank you for your understanding!

I'm not suggesting you remove ReferenceAssemblyAnnotator or netstandard 2.0 support. The former just needs fixed so that it doesn't break when targeting multiple framework versions.

[christophwille]

@ds5678 please open a new issue if ever the ReferenceAssemblyAnnotator bug gets fixed and we can thus support trimming.