Possible Regression from 3.0 to 4.X

[PhilShipley]

Hi Daniel, I'm back (again).

I am having a specific issue. Perhaps you have some insight(s). The issue begins at SharpIppNext 4.0.0.

The consuming project is a classic C# UWP Print Support App targeting Release|x64 with the legacy .NET Native compiler (nutc_driver.exe 2.2.12).
Visual Studio 2026 and/or 2022 doesn't seem to matter.

SharpIppNext is referenced by a C# Windows Runtime Component.
The component alone builds successfully in Release.

When the component is referenced by the final PSA UWP app, the PSA's .NET Native compilation hangs indefinitely (hours) at: “Scanning 132231 methods”. Release only, Debug is fine

SharpIppNext 3.0.0 succeeds; SharpIppNext 4.0.0+ reproduces.
The PSA resolves the netstandard2.0 asset, not net8.0/net10.0.

One obvious difference I see is the additional dependency for System.ComponentModel.Annotations in the 4.X chain.
It may have changed the resolved dependency graph.

Not certain if there is anything that can be done, but figured I'd ask and/or put it out there for your comments.

[danielklecha]

I'm always happy to hear feedback :)

1. I will consider future optimizations to MapperConstructorExtensions to avoid generating redundant generic delegate combinations if we want to reduce the AOT method footprint.
2. Try to use 64-bit .NET Native Compiler in your .csproj: <Use64BitCompiler>true</Use64BitCompiler>
3. Ensure UWP app's Default.rd.xml doesn't have open-ended reflection directives scanning all referenced assemblies with Dynamic="Required All".
4. Try to use <UseDotNetNativeSharedAssemblyFramework>true</UseDotNetNativeSharedAssemblyFramework>

[PhilShipley]

Hi @danielklecha:

Thanks for your reply.
I tried the suggestions you detailed above (2 - 4), but still without success.

[danielklecha]

@PhilShipley One more idea - could you edit Default.rd.xml and add <Assembly Name="System.ComponentModel.Annotations" Dynamic="Excluded" />? Will it help?
I will try to abandon System.ComponentModel.Annotations and improve mapper. I will let you know when I prepare new code.

[PhilShipley]

@danielklecha, no luck with that parameter.