Skip to content
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

Add documentation for the ContainerPublishInParallel MSbuild property #45547

Open
baronfel opened this issue Mar 27, 2025 · 0 comments
Open

Add documentation for the ContainerPublishInParallel MSbuild property #45547

baronfel opened this issue Mar 27, 2025 · 0 comments
Assignees
Labels
dotnet-fundamentals/svc 📌 seQUESTered Identifies that an issue has been imported into Quest.

Comments

@baronfel
Copy link
Member

baronfel commented Mar 27, 2025

Type of issue

Typo

Description

When making multi-RID containers, some project types (blazor, wasm especially) have race conditions in the build. While we work to solve this at a root level, we've added a flag to 8.0.408, 9.0.300 and 10.0 that lets users control this parallelism.

The PR that added the feature is dotnet/sdk#47455.

By default, we publish for each inner RID in parallel. If ContainerPublishInParallel is set to false, then we will publish each RID sequentially - this will make the publish take longer, but it will be much more stable.

[Enter feedback here]

Page URL

https://learn.microsoft.com/en-us/dotnet/core/containers/publish-configuration

Content source URL

https://github.com/dotnet/docs/blob/main/docs/core/containers/publish-configuration.md

Document Version Independent Id

87603b1d-8af0-ecb0-fca2-aacd3d7ef5a0

Platform Id

36de283b-4744-4f85-0ab2-e0ce83954d51

Article author

@gewarren

Metadata

  • ID: a8539d30-07b2-29ff-8e9b-09d83bc066e5
  • PlatformId: 36de283b-4744-4f85-0ab2-e0ce83954d51
  • Service: dotnet-fundamentals

Related Issues


Associated WorkItem - 417519

@dotnet-policy-service dotnet-policy-service bot added the ⌚ Not Triaged Not triaged label Mar 27, 2025
@gewarren gewarren self-assigned this Apr 4, 2025
@dotnetrepoman dotnetrepoman bot added the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Apr 4, 2025
@gewarren gewarren added 🗺️ reQUEST Triggers an issue to be imported into Quest. and removed 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. labels Apr 4, 2025
@dotnet-policy-service dotnet-policy-service bot removed the ⌚ Not Triaged Not triaged label Apr 4, 2025
@sequestor sequestor bot added 📌 seQUESTered Identifies that an issue has been imported into Quest. and removed 🗺️ reQUEST Triggers an issue to be imported into Quest. labels Apr 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dotnet-fundamentals/svc 📌 seQUESTered Identifies that an issue has been imported into Quest.
Projects
Status: 🔖 Ready
Development

No branches or pull requests

2 participants