building on build server and assure projects are correctly build / published

[rekna1]

Build workflow on build server

I had the following situation on a buildserver
A dotnet core application that uses DPAPI was build as self contained exe with a version of dotnet 6 that did not support DPAPI.
So I installed that latest SDK on the build server and restarted the server and tried dotnet publish again.
However the dotnet publish command did not (completely?) rebuild the program, so the error persisted. (Did it still included the dotnet runtime from the previous build on the older sdk ?)
It was not until I had manually cleaned all bin and obj folders the program was rebuild correctly and the error disappeared.

So my question is if there is a workflow using the dotnet command, to ensure a full rebuild and publish of the project without having to clean bin / obj folders manually?

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 211afdc7-c796-202d-239d-823f2a499dff
• Version Independent ID: 9439897e-dcb3-bc2e-5cae-35c1ca2e0681
• Content: dotnet publish command - .NET CLI
• Content Source: docs/core/tools/dotnet-publish.md
• Product: dotnet-fundamentals
• Technology: dotnet-cli
• GitHub Login: @tdykstra
• Microsoft Alias: tdykstra

[tdykstra]

@baronfel who could answer this question?

[baronfel]

Without seeing a binlog of the two builds it's hard to tell - I'd suggest raising issues like this to dotnet/sdk for triage and analysis, and then any findings/guidance from that process could end up in this repo.