Assigning GUIDs to C# projects

We are also using Azure DevOps, and we have added a PowerShell script in our build pipeline to assign missing ProjectGuids before running any of the SonarCloud tasks. This eliminates a manual effort that devs often forget. However, since guids are added only to the build’s current local copy of the code, they change with every build. As far as I can tell, this seems to be ok, though. The results on SonarCloud seem to correctly differentiate issues with new code vs old code.

Am I missing something? What are the consequences of projectguids that change from build to build?

hi @benjiecov

Welcome to our community. Please always start a new topic for your discussion - I’ve split this to a new post.

I don’t understand if you have a problem there… Could you please rephrase your ask?