Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

.NET Native Support #292

Open
austinbhale opened this issue Sep 8, 2023 · 0 comments
Open

.NET Native Support #292

austinbhale opened this issue Sep 8, 2023 · 0 comments

Comments

@austinbhale
Copy link
Contributor

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant