-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Don't set PublishAot in SDK by default #74046
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
Conversation
LakshanF
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
|
/backport to release/7.0-rc1 |
|
Started backporting to release/7.0-rc1: https://github.com/dotnet/runtime/actions/runs/2872323345 |
|
I did some amount of validation locally on a selection of the SDK tests that were failing in dotnet/sdk#27149 and am seeing them pass with this change. |
|
/azp run runtime-wasm |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Also, |
Props files don't know what we're going to target because they're included before users csproj that has those details. WASM builds include Windows targeting-related-props files as well; it's fine. They're not supposed to have side effects like this bug had, just set up the environment in a user-overridable way. |
Opening this as an alternative to reverting the PublishAot changes in #74036.
The intention was to default PublishAot to true when using the package reference, not when using the ILCompiler that ships with the SDK. These props get imported on both paths - I think it was just missing a check.