Replies: 2 comments 1 reply
-
You can compare the bits of publish results to start. |
Beta Was this translation helpful? Give feedback.
-
In the <PropertyGroup>
<RuntimeIdentifiers>win-x64;linux-x64;arch-x64;rhel-x64;osx-x64;osx-arm64</RuntimeIdentifiers>
</PropertyGroup> For the actual publish you need to specify which rid should be used -- as you do already, as can be seen from you question.
AFAIK yes, there are negative effects, as the But try specifying the rids in the project, so that the expensive restore needs to be done only once. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I have a script which publish to multiple runtimes: win-x64, linux-x64, arch-x64, rhel-x64, osx-x64, osx-arm64.
All of them execute sequential with
dotnet publish $project -o "$publishFolder/$publishName" -c Release -r $runtime -p:PublishReadyToRun=true --self-contained
but i notice this is a bit slow, it takes +/- 11m to finish.My question is if i do
dotnet build $project -c Release
(Generic build without runtime) and then pass--no-build
on each publish, will it have any negative effect?Also to speed up publishes, can i parallel the publishes? 1 publish per task/core? Since each publish create it own folder under /bin, it should not be a problem right?
Beta Was this translation helpful? Give feedback.
All reactions