I currently have a team working on a .NET core project in combination with our SonarCloud subscription.
As you can see in the screenshot they have 2 msbuild tasks, but also 2 .net core builds in their build definition.
The .net core builds do not run any sonar analysis.
I already asked the team if they could use MSbuild instead of the .net core build. But they do not really prefer this.
What should be the supported scenario for this situation?
after talking to the team, it looks like this is not supported to trigger one single analysis for such a “multiple build” build definition. A solution in this case is to have dedicated build definitions for each .NET solution.
Which extension do you mean? We use the SonarQube tasks as we cannot use the SonarCloud tasks in TFS.
The SonarQube prepare task gives us the option “Integrate MSBUILD”, “Maven or Gradle” and “Use Standalone scanner”. We do not see any option for .NET core.