Skip to content

Warning caused by EnableAOTAnalyzer points to IsAotCompatible #34505

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.

Sign up for GitHub

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

Jump to bottom
Closed
sbomer opened this issue Aug 8, 2023 · 0 comments · Fixed by #35186
Closed

Warning caused by EnableAOTAnalyzer points to IsAotCompatible #34505

sbomer opened this issue Aug 8, 2023 · 0 comments · Fixed by #35186
Assignees
@sbomer
Labels
Area-NetSDK untriaged Request triage from a team member

Comments

@sbomer
Copy link
Member

sbomer commented Aug 8, 2023

When EnableAOTAnalyzer is set in a project that has a TFM where AOT analysis isn't supported, we produce the following warning:

IsAotCompatible is not supported for the target framework. Consider multi-targeting to a supported framework to enable ahead-of-time compilation analysis, and set IsAotCompatible only for the supported frameworks. [...]

Our recommendation is to set IsAOTCompatible instead of EnableAOTAnalyzer. We made the warning point to EnableAOTAnalyzer under the assumption that this would be the most common way to enable the analyzer, but the warning message is confusing when it was enabled directly through EnableAOTAnalyzer.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sbomer sbomer

Labels
Area-NetSDK untriaged Request triage from a team member
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Adjust trim/aot warning messages sbomer/sdk
1 participant
@sbomer