This is the current way to exclude .NET projects from the analysis.
To give some explanation: how our analysis currently works is that the Roslyn analyzers run during the build, and the results are then filtered during the END step based on the exclusions patterns.
To exclude the projects from the analysis (to avoid the performance overhead of running Roslyn analysis during compilation), you need to add the <SonarQubeExclude>true</SonarQubeExclude> in the {cs,vb}proj to exclude (like mentioned in the docs).
that was never in question that this would work. the problem is that the SonarExclusions as defined on your website are applied to every CSPROJ in the solution and that doesnât seem right. I would want to enter relative paths relative to the root of the repo or solution. But if i say exclude âUtilitiesâ, it excludes the Utilities folder in every single CSPROJ in the solution. That just doesnât seem correct to me.