-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
More settings for maintaining consistency between AOT and non-AOT mode #82368
Comments
Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas Issue DetailsI want to make something that works consistently with PublishAot, so that we can have a fast development cycle in Debug mode, while in Release and Publish we use AOT. This mean I want the entire project to:
All of which is not easily achivable or simply isn't possible in the current AOT mode yet. Let's fix that.
|
We have Roslyn static analyzers that help with flagging trimming and AOT issues before you build the source code. They're enabled by default with Typically, you shouldn't see AOT-specific issues that were not flagged by the analyzers ahead of time and if you do, please let us know about them. Do you see issues that were not flagged by the analyzers? We don't currently have plans for incremental AOT rebuilds because one should only need them rarely. |
This issue has been marked |
This issue has been automatically marked |
This issue will now be closed since it had been marked |
I want to make something that works consistently with PublishAot, so that we can have a fast development cycle in Debug mode, while in Release and Publish we use AOT.
This mean I want the entire project to:
All of which is not easily achivable or simply isn't possible in the current AOT mode yet. Let's fix that.
The text was updated successfully, but these errors were encountered: