Add escape hatch for publishing with SelfContained=true, but no RuntimeIdentifier.#36047
Merged
nagilson merged 1 commit intodotnet:mainfrom Oct 13, 2023
Conversation
…meIdentifier. This is identical to issue dotnet#33414 (allow PublishAot=true without RuntimeIdentifier), except for the SelfContained property instead of the PublishAot property. This adds an escape hatch for a sanity check when trying to publish with SelfContained=true, but without a RuntimeIdentifier, because the check is not valid when building universal apps for macOS and Mac Catalyst (the netX-macos and netX-maccatalyst target frameworks). When building such an app, the project file will set RuntimeIdentifiers (plural): <TargetFramework>net8.0-macos</TargetFramework> <RuntimeIdentifiers>osx-x64;osx-arm</RuntimeIdentifiers> and then during the build, the macOS SDK will run two inner builds, with RuntimeIdentifiers unset, and RuntimeIdentifier set to each of the rids (and at the end merge the result into a single app). The problem is that the outer build, where RuntimeIdentifiers is set, but RuntimeIdentifier isn't, triggers the sanity check if the developer sets SelfContained=true, and that fails the build. Note that SelfContained defaults to true if PublishTrimmed=true, which means that just setting PublishTrimmed=true also triggers the sanity check. Ref: dotnet/macios#19142
ghost
added
Member
Author
Member
Author
|
This is a breaking change in .NET 8 for us, so it would be nice to get it backported as well, if possible. |
dsplaisted
approved these changes
Oct 12, 2023
Member
|
Eventually, once we have better support for TargetFramework aliasing (NuGet/Home#12124), I'd like to see if we can change the pattern from this: <TargetFramework>net8.0-macos</TargetFramework>
<RuntimeIdentifiers>osx-x64;osx-arm</RuntimeIdentifiers>To something like this, which would use more of the built-in multi-targeting support: <TargetFrameworks>net8.0-macos/osx-x64;net8.0-macos/osx-arm</TargetFrameworks> |
Member
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
nagilson
approved these changes
Oct 12, 2023
Member
|
/backport to release/8.0.2xx |
Contributor
|
Started backporting to release/8.0.2xx: https://github.com/dotnet/sdk/actions/runs/6498791126 |
Member
|
@marcpopMSFT can we backport this to |
Member
|
/backport to release/8.0.1xx |
Contributor
|
Started backporting to release/8.0.1xx: https://github.com/dotnet/sdk/actions/runs/7118004282 |
jonathanpeppers
added a commit
that referenced
this pull request
Apr 22, 2025
…sage (#48624) Context: #36047 Context: dotnet/android#10062 We have experimental support for CoreCLR+R2R on Android. Android is also unique in that a default build can target multiple RIDs via: <RuntimeIdentifiers>android-arm;android-arm64;android-x86;android-x64</RuntimeIdentifiers> Unfortunately, targeting 4 RIDs like this results in: dotnet/sdk/10.0.100-preview.4.25180.3/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.RuntimeIdentifierInference.targets(219,5): error NETSDK1191: A runtime identifier for the property 'PublishReadyToRun' couldn't be inferred. Specify a rid explicitly But simply skipping this error message allows the build to succeed, and R2R successfully runs on all 4 RIDs. Just like in d21e6bf, I introduced a new `$(AllowReadyToRunWithoutRuntimeIdentifier)` property to opt out of this error message. I also added `$(AllowPublishSingleFileWithoutRuntimeIdentifier)`, to give the same flexibility in the future.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is identical to issue #33414 (allow PublishAot=true without RuntimeIdentifier), except for the SelfContained property instead of the PublishAot property.
This adds an escape hatch for a sanity check when trying to publish with SelfContained=true, but without a RuntimeIdentifier, because the check is not valid when building universal apps for macOS and Mac Catalyst (the netX-macos and netX-maccatalyst target frameworks).
When building such an app, the project file will set RuntimeIdentifiers (plural):
and then during the build, the macOS SDK will run two inner builds, with RuntimeIdentifiers unset, and RuntimeIdentifier set to each of the rids (and at the end merge the result into a single app).
The problem is that the outer build, where RuntimeIdentifiers is set, but RuntimeIdentifier isn't, triggers the sanity check if the developer sets SelfContained=true, and that fails the build.
Note that SelfContained defaults to true if PublishTrimmed=true, which means that just setting PublishTrimmed=true also triggers the sanity check.
Ref: dotnet/macios#19142