Skip to content

Fix multi-platform project container builds (RuntimeIdentifiers passed as one RID) - #21514

Merged
David Fowler (davidfowl) merged 5 commits into
mainfrom
aspireagent/fix-container-rid-list-9281
Nov 11, 2026
Merged

David Fowler (davidfowl) merged 5 commits into
mainfrom
aspireagent/fix-container-rid-list-9281

Conversation

@davidfowl

@davidfowl David Fowler (davidfowl) commented Oct 31, 2026 •

Copy link
Copy Markdown
Collaborator

Description

What failed

Multi-platform container builds of .NET programs fail in 13.6. With WithContainerBuildOptions(ctx => ctx.TargetPlatform = ContainerTargetPlatform.AllLinux), project builds fail like this (report on #9281):

error NETSDK1083: The specified RuntimeIdentifier 'linux-x64;linux-arm64' is not recognized.

File-based apps (dotnet publish app.cs) fail the same way, and quoting the list alone makes them fail differently:

error NETSDK1083: The specified RuntimeIdentifier '"linux-x64' is not recognized.
error NETSDK1083: The specified RuntimeIdentifier 'linux-arm64"' is not recognized.

Two related multi-platform problems surfaced in review:

  • A file-based app with a build environment (WithDotnetProgramBuildEnvironment) fails with MSBUILD : error MSB1006: Property is not valid. Switch: linux-arm64.
  • An app or project that defines or inherits RuntimeIdentifier / ContainerRuntimeIdentifier publishes successfully but produces a single-platform image.

Why

#19997 moved AddTargetPlatformArguments to MsBuildResponseFileFactory.CreatePropertyArgument, which percent-escapes ; as %3B. That stops MSBuild's command-line parser from splitting the switch. But an escaped ; also stays literal when MSBuild expands the property into items, so the SDK sees one RID, linux-x64;linux-arm64. Before #19997 the list was passed quoted, which is why 13.5.x worked.

Project files and file-based apps parse the switch differently:

  • Project files (dotnet msbuild / dotnet publish app.csproj): MSBuild's switch parser splits an unquoted value on ;, so the list has to be quoted.
  • File-based apps (dotnet build|publish app.cs): the .NET CLI parses the switch itself and passes it to the virtual project as a global property. It keeps quote characters literally, and it appends ; segments without = to the previous value. So the list has to be unquoted.

Two further causes:

  • Response file: the build-environment response file wrapped each switch in quotes. The .NET CLI does not recognize a quoted switch for a file-based app, so it treated app.cs as an MSBuild argument and handed everything to MSBuild, which then split the unquoted RID list.
  • Singular RIDs: the SDK prefers RuntimeIdentifier and ContainerRuntimeIdentifier over the plural lists, and can derive the container RID from RuntimeIdentifier. Any inherited or project-defined singular value therefore wins over the lists.

Fix

  • MsBuildResponseFileFactory.CreateListPropertyArgument percent-escapes each entry and joins them with real ; inside quotes (--property:RuntimeIdentifiers="linux-x64;linux-arm64"). This is used for project files.
  • MsBuildResponseFileFactory.CreateFileBasedAppListPropertyArgument emits the same list without quotes (--property:RuntimeIdentifiers=linux-x64;linux-arm64). This is used for file-based apps.
  • AddTargetPlatformArguments chooses between them using IProjectMetadata.IsFileBasedApp. It applies to RuntimeIdentifiers and ContainerRuntimeIdentifiers for both the publish command and the ContainerWorkingDirectory query. Single-RID and all other properties are unchanged.
  • For multi-platform targets, AddTargetPlatformArguments also emits --property:RuntimeIdentifier= and --property:ContainerRuntimeIdentifier= before the lists, so singular defaults cannot collapse the build into one image.
  • MsBuildResponseFileFactory.CreateAsync takes isFileBasedApp. File-based apps get one unquoted --property:Name=value; per line. The trailing ; is consumed by the CLI parser and stops it from trimming trailing Unicode whitespace; values are still percent-escaped. Projects keep whole-switch quotes, and the project-only Aspire.Hosting.Dotnet caller passes false.

Confidence

High for both paths. Each form was checked through a real SDK container publish for linux-x64 + linux-arm64, and each path now has a test that runs the CLI parser actually used for it. The 14 tests that load real images into Docker didn't run locally (see Validation); CI runs them.

How we stop this recurring

  • BuildImageAsync_MultiPlatformArgumentsSurviveMsBuildParsing round-trips the emitted switches through the real parser for each path: dotnet msbuild properties.proj for projects and dotnet build app.cs (via Directory.Build.props) for file-based apps. It asserts both the property string and the item expansion (["linux-x64", "linux-arm64"]). The probe also defines both singular RIDs and asserts that they evaluate empty. Before, the file-based variant probed a synthetic .proj, so it couldn't see the file-based app behaviour.
  • New CanBuildMultiPlatformArchiveFromFileBasedCSharpApp runs a real AllLinux OCI archive publish of an app.cs through IResourceContainerImageManager. It asserts that the archive's image index contains linux/amd64 and linux/arm64. It has three cases: plain, with a build environment (response-file path), and with RuntimeIdentifier / ContainerRuntimeIdentifier set in the app. The archive reader only reads index.json and the index blobs, not the layers.

Before/after evidence

File-based app, real SDK publish (dotnet publish app.cs /t:PublishContainer, archive output, SDK 11.0.100-rc.2):

RuntimeIdentifiers switch value Result
"linux-x64;linux-arm64" (previous commit) NETSDK1083 ... '"linux-x64' / 'linux-arm64"'
linux-x64%3Blinux-arm64 (main) NETSDK1083 ... 'linux-x64;linux-arm64'
linux-x64;linux-arm64 (this PR) Builds both RIDs, creates the image index and writes the archive

Project, real SDK publish (dotnet new web, same switches): %3B fails with NETSDK1083 ('linux-x64;linux-arm64'). The quoted list builds linux-x64 and linux-arm64 images and an image index.

Response file, real SDK publish (dotnet publish app.cs, AllLinux OCI archive, @file.rsp): "--property:Foo=bar" fails with MSB1006 ... Switch: linux-arm64; --property:Foo=bar; writes the archive.

Singular RID, real SDK publish (app.cs with #:property RuntimeIdentifier=linux-x64, AllLinux OCI archive): without the empty singular properties, the archive has one image with no platform. With them, it has linux/amd64 and linux/arm64.

Regression tests, before (fix reverted in src/) and after:

  • CanBuildMultiPlatformArchiveFromFileBasedCSharpApp: before, it fails with NETSDK1083: The specified RuntimeIdentifier '"linux-x64' is not recognized. After, it passes.
  • BuildImageAsync_MultiPlatformArgumentsSurviveMsBuildParsing(fileBased: True): before, it fails on the emitted arguments. After, it passes.
  • CanBuildMultiPlatformArchiveFromFileBasedCSharpApp(withBuildEnvironment: True): before, it fails with MSB1006 ... Switch: linux-arm64. After, it passes.
  • CanBuildMultiPlatformArchiveFromFileBasedCSharpApp(withProjectRuntimeIdentifiers: True): before, Expected "linux/amd64", Actual "/" (single image). After, it passes.
  • BuildImageAsync_MultiPlatformArgumentsSurviveMsBuildParsing (both variants): before, they fail on the missing empty singular RIDs. After, they pass.
  • CanBuildArchiveFromFileBasedCSharpApp passes in both runs.

Validation

  • ResourceContainerImageBuilderTests, DotnetProgramPublishingTests and DockerContainerRuntimeTests: 118 passed, 0 failed locally. This includes both real file-based archive publishes. I excluded 14 tests that load real images into Docker, because this machine runs out of disk for base-image layers. CI runs them.
  • src/Aspire.Hosting.Dotnet, which also compiles the shared MsBuildResponseFile.cs, builds cleanly. Its DotnetProjectBuildEnvironmentTests pass. Five DotnetProjectBuildCoordinatorTests (traversal restore and context-specific build) fail on this machine both with and without this change, so those failures are environmental.
  • main was merged in so I could update WslcDotnetPublishingTests.DotnetPublishing_ArchiveDoesNotInvokeWslc (from Add initial WSLc publish/deploy support with explicit capability limits #21009) to expect the quoted RID list for projects; the multi-platform expectation now also includes the empty singular RIDs. That class is Windows-only (SkipOnPlatform on Linux and macOS), so the Windows CI job verifies it.

Fixes #9281

Checklist

  • Is this feature complete?
    • Yes. Ready to ship.
    • No. Follow-up changes expected.
  • Are you including unit tests for the changes and scenario tests if relevant?
    • Yes
    • No
  • Did you add public API?
    • Yes
      • If yes, did you have an API Review for it?
        • Yes
        • No
      • Did you add <remarks /> and <code /> elements on your triple slash comments?
        • Yes
        • No
    • No
  • Does the change make any security assumptions or guarantees?
    • Yes
      • If yes, have you done a threat model and had a security review?
        • Yes
        • No
    • No

🤖 Posted by AspireAgent (AI Agent)

Percent-escaping ';' in the RuntimeIdentifiers/ContainerRuntimeIdentifiers
switches made MSBuild treat 'linux-x64;linux-arm64' as a single RID, so
multi-platform project container builds failed with NETSDK1083. Escape each
RID and quote the list so ';' stays a real item separator.

Fixes #9281

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@github-actions

Copy link
Copy Markdown
Contributor

🚀 Dogfood this PR with:

⚠️ WARNING: Do not do this without first carefully reviewing the code of this PR to satisfy yourself it is safe.

curl -fsSL https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 21514

Or

  • Run remotely in PowerShell:
iex "& { $(irm https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 21514"

@github-actions github-actions Bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Oct 31, 2026
@aspire-repo-bot
aspire-repo-bot Bot requested a balanced review from Copilot October 31, 2026 02:37
@github-actions

This comment has been minimized.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

No active review issues are recorded for the change addressing multi-platform runtime identifier handling.

No open issues 🎉

What changed in this PR

Fixes a regression in Aspire’s multi-platform .NET container publishing where MSBuild treated multiple runtime identifiers as one value, causing NETSDK1083.

Changes:

  • Adds a list-property argument helper that escapes individual entries while preserving quoted semicolon separators.
  • Uses the helper for multi-platform runtime properties, leaving single-platform arguments unchanged.
  • Strengthens regression tests to verify that MSBuild expands both runtime properties into separate items.
File Description
tests/​Aspire.Hosting.Tests/​Publishing/​ResourceContainerImageManagerTests.cs Verifies quoted arguments and separate runtime items for project and file-based builds.
src/​Shared/​MsBuildResponseFile.cs Adds argument formatting for list-valued MSBuild properties.
src/​Aspire.Hosting/​Publishing/​ResourceContainerImageManager.cs Applies list formatting to multi-platform runtime properties.

Review effort: Balanced

Copy link
Copy Markdown
Collaborator Author

CI note for exact head 2e08ef3f, run 41160826284. Attempt 1 had 331 passing checks and 5 failures. None of the failures is in code this PR touches. All 5 are known infrastructure problems on Windows, so I reran the failed jobs once:

Job Attempt 1
Hosting.Java (windows-latest) The hosted runner lost communication with the server (log BlobNotFound)
VS Code extension E2E (Windows, command-palette) The hosted runner lost communication with the server
VS Code extension E2E (Windows, dynamic-debug-configuration) The hosted runner lost communication with the server
VS Code extension E2E (Windows, coordinated-build) The hosted runner lost communication with the server
Aspire CLI Starter Validation (Windows x64) Exceeded the 45m maximum execution time in "Create starter app and validate startup" (known hung Windows CLI-starter job)

🤖 Posted by AspireAgent (AI Agent)

@davidfowl David Fowler (davidfowl) added the agent:working An AI agent is actively working on this issue or PR label Nov 11, 2026 — with Copilot SWE Agent

David Fowler (davidfowl) commented Nov 11, 2026 •

Copy link
Copy Markdown
Collaborator Author

AspireAgent stopped: Ankit Jain (@radical)'s file-based app feedback is addressed and Final Results is green on 232eb0f.

🤖 Posted by AspireAgent (AI Agent)

`dotnet publish app.cs` parses property switches in the .NET CLI and keeps
quote characters, so the quoted RuntimeIdentifiers list failed with
NETSDK1083 for '"linux-x64'. File-based apps now get the unquoted list;
project-based builds keep the quoted form MSBuild needs.

Adds a real file-based multi-platform archive publish test and probes the
file-based argument round trip through `dotnet build app.cs`.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@github-actions

This comment has been minimized.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

The test unnecessarily buffers and copies every archive entry, including both architectures’ filesystem layers, even though the assertion only needs index metadata.

1 open issue

Review effort: Balanced

@github-actions

Copy link
Copy Markdown
Contributor

Retrying the failed CI jobs for this pull request from the CI run attempt. The rerun is being tracked in the rerun attempt.

@github-actions

Copy link
Copy Markdown
Contributor

Retrying the failed CI jobs for this pull request from the CI run attempt. The rerun is being tracked in the rerun attempt.

#21009 added an expectation for the percent-escaped
RuntimeIdentifiers list; project builds now pass the quoted list.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copy link
Copy Markdown
Collaborator Author

I merged main into this branch (190e4da) only so I could update WslcDotnetPublishingTests.DotnetPublishing_ArchiveDoesNotInvokeWslc from #21009. That test still expected the old %3B-escaped RuntimeIdentifiers list, so it failed against this PR's quoted RID list for projects. 232eb0f changes only that expectation and makes no other logic changes.

🤖 Posted by AspireAgent (AI Agent)

@radical Ankit Jain (radical) left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[automated] Two related, pre-existing multi-platform publishing issues remain. I reproduced both and validated the suggested fixes locally against the pre-merge head 655dcf3; neither fix is in the current PR head.

Comment thread src/Shared/MsBuildResponseFile.cs Resolved
@github-actions

This comment has been minimized.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔵 Needs a closer look

The test unnecessarily retains all archive entries and copies each with ToArray(), adding memory and GC pressure when only the JSON indexes are needed.

1 open issue

Review effort: Balanced

@github-actions

Copy link
Copy Markdown
Contributor

Retrying the failed CI jobs for this pull request from the CI run attempt. The rerun is being tracked in the rerun attempt.

@github-actions

Copy link
Copy Markdown
Contributor

Retrying the failed CI jobs for this pull request from the CI run attempt. The rerun is being tracked in the rerun attempt.

@davidfowl David Fowler (davidfowl) removed the agent:working An AI agent is actively working on this issue or PR label Nov 11, 2026
@davidfowl David Fowler (davidfowl) added the agent:working An AI agent is actively working on this issue or PR label Nov 11, 2026 — with Copilot SWE Agent

David Fowler (davidfowl) commented Nov 11, 2026 •

Copy link
Copy Markdown
Collaborator Author

AspireAgent is addressing Ankit Jain (@radical)'s response-file and singular-RID review threads.

🤖 Posted by AspireAgent (AI Agent)

…latform builds

- Write build-environment response-file switches unquoted with a trailing ';' for
  file-based apps; the .NET CLI rejected whole-switch quotes and fell back to MSBuild
  (MSB1006 for linux-arm64 on AllLinux).
- Clear RuntimeIdentifier and ContainerRuntimeIdentifier for multi-platform targets so
  inherited or project-defined singular RIDs cannot collapse the build to one image.
- Extend the real file-based AllLinux publish test with build-environment and
  project-RID cases, and read only OCI index entries from the archive.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@github-actions

Copy link
Copy Markdown
Contributor

Tests selector

52 / 101 PR test projects · 4 PR jobs, from 5 changed files.

Selected PR test projects (52 / 101)

Aspire.Cli.EndToEnd.Tests, Aspire.Hosting.Analyzers.Tests, Aspire.Hosting.Azure.EntraId.Tests, Aspire.Hosting.Azure.Kubernetes.Tests, Aspire.Hosting.Azure.Kusto.Tests, Aspire.Hosting.Azure.Provisioning.Tests, Aspire.Hosting.Azure.Tests, Aspire.Hosting.Blazor.Tests, Aspire.Hosting.Browsers.Tests, Aspire.Hosting.CodeGeneration.Go.Tests, Aspire.Hosting.CodeGeneration.Java.Tests, Aspire.Hosting.CodeGeneration.Python.Tests, Aspire.Hosting.CodeGeneration.Rust.Tests, Aspire.Hosting.CodeGeneration.TypeScript.Tests, Aspire.Hosting.Containers.Tests, Aspire.Hosting.DevTunnels.Tests, Aspire.Hosting.Docker.Tests, Aspire.Hosting.Dotnet.Tests, Aspire.Hosting.DotnetTool.Tests, Aspire.Hosting.EntityFrameworkCore.Tests, Aspire.Hosting.Foundry.Tests, Aspire.Hosting.Garnet.Tests, Aspire.Hosting.Go.Tests, Aspire.Hosting.Java.Tests, Aspire.Hosting.JavaScript.Tests, Aspire.Hosting.Kafka.Tests, Aspire.Hosting.Keycloak.Tests, Aspire.Hosting.Kubernetes.Tests, Aspire.Hosting.Maui.Tests, Aspire.Hosting.Milvus.Tests, Aspire.Hosting.MongoDB.Tests, Aspire.Hosting.MySql.Tests, Aspire.Hosting.Nats.Tests, Aspire.Hosting.OpenAI.Tests, Aspire.Hosting.Oracle.Tests, Aspire.Hosting.Orleans.Tests, Aspire.Hosting.PostgreSQL.Tests, Aspire.Hosting.Python.Tests, Aspire.Hosting.Qdrant.Tests, Aspire.Hosting.RabbitMQ.Tests, Aspire.Hosting.Radius.Tests, Aspire.Hosting.Redis.Tests, Aspire.Hosting.RemoteHost.Tests, Aspire.Hosting.Rust.Tests, Aspire.Hosting.Seq.Tests, Aspire.Hosting.SqlServer.Tests, Aspire.Hosting.Testing.Tests, Aspire.Hosting.Tests, Aspire.Hosting.Valkey.Tests, Aspire.Hosting.Yarp.Tests, Aspire.Playground.Tests, Aspire.Templates.Tests

Selected PR jobs (4)

cli-starter-validation, extension-e2e, polyglot, typescript-api-compat


How these were chosen — grouped by what changed

⚠️ 32 of the 52 selected test projects come from a single change — src/Aspire.Hosting/Publishing/ResourceContainerImageManager.cs.

🔧 src/Aspire.Hosting/Publishing/ResourceContainerImageManager.cs (changed source)
→ 32 via the project graph

show 32

Aspire.Hosting.Analyzers.Tests (2 hops), Aspire.Hosting.Azure.Kusto.Tests (2 hops), Aspire.Hosting.Azure.Provisioning.Tests (3 hops), Aspire.Hosting.Browsers.Tests (2 hops), Aspire.Hosting.CodeGeneration.Go.Tests, Aspire.Hosting.CodeGeneration.Java.Tests, Aspire.Hosting.CodeGeneration.Python.Tests, Aspire.Hosting.CodeGeneration.Rust.Tests, Aspire.Hosting.Containers.Tests (2 hops), Aspire.Hosting.Garnet.Tests (2 hops), Aspire.Hosting.Go.Tests (2 hops), Aspire.Hosting.Java.Tests (2 hops), Aspire.Hosting.JavaScript.Tests (2 hops), Aspire.Hosting.Kafka.Tests (2 hops), Aspire.Hosting.Keycloak.Tests (2 hops), Aspire.Hosting.Maui.Tests, Aspire.Hosting.MongoDB.Tests (2 hops), Aspire.Hosting.MySql.Tests (2 hops), Aspire.Hosting.Nats.Tests (2 hops), Aspire.Hosting.OpenAI.Tests (2 hops), Aspire.Hosting.Oracle.Tests (2 hops), Aspire.Hosting.Orleans.Tests (2 hops), Aspire.Hosting.PostgreSQL.Tests (2 hops), Aspire.Hosting.Python.Tests (2 hops), Aspire.Hosting.RabbitMQ.Tests (2 hops), Aspire.Hosting.Redis.Tests (2 hops), Aspire.Hosting.Rust.Tests (2 hops), Aspire.Hosting.Seq.Tests (2 hops), Aspire.Hosting.SqlServer.Tests (2 hops), Aspire.Hosting.Valkey.Tests (2 hops), Aspire.Hosting.Yarp.Tests (2 hops), Aspire.Playground.Tests

🔧 src/Aspire.Hosting.Dotnet/DotnetProjectBuildEnvironment.cs (changed source)
→ 3 directly: Aspire.Cli.EndToEnd.Tests, Aspire.Hosting.Dotnet.Tests, Aspire.Templates.Tests
→ 15 via the project graph

show 15

Aspire.Hosting.Azure.EntraId.Tests, Aspire.Hosting.Azure.Kubernetes.Tests (2 hops), Aspire.Hosting.Azure.Tests, Aspire.Hosting.CodeGeneration.TypeScript.Tests, Aspire.Hosting.DevTunnels.Tests, Aspire.Hosting.Docker.Tests, Aspire.Hosting.DotnetTool.Tests (2 hops), Aspire.Hosting.EntityFrameworkCore.Tests, Aspire.Hosting.Foundry.Tests, Aspire.Hosting.Kubernetes.Tests, Aspire.Hosting.Milvus.Tests, Aspire.Hosting.Qdrant.Tests, Aspire.Hosting.Radius.Tests, Aspire.Hosting.RemoteHost.Tests, Aspire.Hosting.Testing.Tests

📦 affected project Aspire.Hosting.Dotnet
→ 2 tests: Aspire.Cli.EndToEnd.Tests, Aspire.Templates.Tests

🧪 tests/Aspire.Hosting.Tests/Publishing/ResourceContainerImageManagerTests.cs (changed test)
→ 1 directly: Aspire.Hosting.Tests
→ 1 via the project graph: Aspire.Hosting.Blazor.Tests

🧪 tests/Aspire.Hosting.Dotnet.Tests/WslcDotnetPublishingTests.cs (changed test)
→ 1 directly: Aspire.Hosting.Dotnet.Tests

Job reasons

Job Triggered by
cli-starter-validation • src/Aspire.Hosting.Dotnet/DotnetProjectBuildEnvironment.cs
• affected project Aspire.Hosting.Dotnet
extension-e2e • src/Aspire.Hosting.Dotnet/DotnetProjectBuildEnvironment.cs, src/Aspire.Hosting/Publishing/ResourceContainerImageManager.cs
• affected project Aspire.Hosting.Dotnet
polyglot • affected project Aspire.Hosting.Dotnet
• affected project Aspire.Hosting.Azure.Provisioning
typescript-api-compat affected project Aspire.Hosting.Dotnet

Selection computed for commit 8d178ba.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

The new file-based response-file format lacks a round-trip test verifying that property values, including escaped semicolons and trailing Unicode whitespace, survive parsing unchanged.

1 open issue
1 resolved since last review

Review effort: Balanced

Comment thread src/Shared/MsBuildResponseFile.cs Resolved
@davidfowl David Fowler (davidfowl) removed the agent:working An AI agent is actively working on this issue or PR label Nov 11, 2026
@davidfowl David Fowler (davidfowl) added the agent:working An AI agent is actively working on this issue or PR label Nov 11, 2026 — with Copilot SWE Agent

David Fowler (davidfowl) commented Nov 11, 2026 •

Copy link
Copy Markdown
Collaborator Author

AspireAgent stopped after verifying merge readiness and submitting the squash merge (operation 2c257db7-ca61-4b70-a8ad-c451a36a1cdc).

🤖 Posted by AspireAgent (AI Agent)

@davidfowl David Fowler (davidfowl) removed the agent:working An AI agent is actively working on this issue or PR label Nov 11, 2026
@davidfowl
David Fowler (davidfowl) merged commit d8cdaa1 into main Nov 11, 2026
365 checks passed
@microsoft-github-policy-service microsoft-github-policy-service Bot added this to the 17.1 milestone Nov 11, 2026
@aspire-repo-bot

Copy link
Copy Markdown
Contributor

✅ No documentation update needed.

Skipped. Branch: docs_optional → bug_fix_restores_documented_behavior (proven false positive).

  • Triggered signal: pr_body_has_cli_flag_mention. Its evidence is the PR body quoting the internal MSBuild argument --property:RuntimeIdentifiers="linux-x64;linux-arm64". That argument is generated internally and is not a user-facing CLI flag.
  • The PR fixes a 13.6 regression where multi-platform container builds of .NET projects and file-based apps failed with NETSDK1083, and fixes related issues with response files and singular RIDs. It restores the behavior that worked in 13.5.x. It adds no new user-facing option, API or setting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area-deployment needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Publishing to docker compose fails for a project with multiple RuntimeIdentifiers

3 participants