Hey there! The MSFT Store has a hard requirement that UWP apps be compiled through the .NET Native tool chain.
To first build a UWP project with the tool chain, all projects referencing MathNet.Numerics.Signed must upgrade to v5.0.0 via this solution.
The core of \psi uses runtime IL generation and reflection. Since UWP acts as a sort of 'sandbox', these operations could represent security vulnerabilities in that the store can't guarantee an app's safety.
For example, creating a new instance of a System.Reflection.Emit.DynamicMethod (e.g., here) will result in System.PlatformNotSupportedException: Dynamic code generation is not supported on this platform. since it seems Native AOT has never supported it, see here.
It seems unlikely that \psi would allow for this, but just wondering if there may be a potential workaround? Thank you!
Hey there! The MSFT Store has a hard requirement that UWP apps be compiled through the .NET Native tool chain.
To first build a UWP project with the tool chain, all projects referencing
MathNet.Numerics.Signedmust upgrade to v5.0.0 via this solution.The core of \psi uses runtime IL generation and reflection. Since UWP acts as a sort of 'sandbox', these operations could represent security vulnerabilities in that the store can't guarantee an app's safety.
For example, creating a new instance of a
System.Reflection.Emit.DynamicMethod(e.g., here) will result inSystem.PlatformNotSupportedException: Dynamic code generation is not supported on this platform.since it seems Native AOT has never supported it, see here.It seems unlikely that \psi would allow for this, but just wondering if there may be a potential workaround? Thank you!