Skip to content
Discussion options

You must be logged in to vote

This way we can find out and weed out problems for NativeAOT for public projects that have unit tests

The way to look for problems is by looking for compile-time warnings. Following article shows how to best approach this for libraries: https://devblogs.microsoft.com/dotnet/creating-aot-compatible-libraries/

Looking for AOT/trimming issues at runtime in a unit test is not a good strategy. Unit tests typically exercise the entire library. So even if the library has a trimming issue, just the fact that it was included from a unit test application that references everything in the library may make the issue go away. The issue could still be real, it's just not observable in a test that use…

Replies: 2 comments

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by MichalStrehovsky
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
3 participants