Scanner should not require a ProjectGuid

[rickardp]

Description

The scanner forces me to add ProjectGuids to all my new SDK-style MSBuild projects, which is cumbersome to say the least, and is also not in line with the new style projects. The scanner should make away with this requirement.

Repro steps

1. dotnet new console

2. Run scanner on project

Expected behavior

Results are uploaded.

Actual behavior

Error:WARNING: Duplicate ProjectGuid: "00000000-0000-0000-0000-000000000000". The project will not be analyzed by SonarQube

Known workarounds

• In text editor, add unique ProjectGuid to all the projects.
  or
• add the projects to a solution and build the solution instead of the individual projects

[duncanp-sonar]

It should be possible to remove this requirement for SonarQube v7.6 or later, but probably not for earlier versions of SonarQube (to maintain backwards-compatibility with projects that have already been analysed).

Prior to the about-to-be-released version 7.6 of SonarQube, individual MSBuild projects were mapped to to SonarQube modules. The ProjectGuid was used as the unique identifier for the module. The concept of modules was dropped in SonarQube v7.6.

[lg2de]

SonarQube 7.6 is available.
Can we easily generate a GUID internally to get a valid analysis?

[jon-is-me]

@duncanp-sonar Just confirming with you, if we upgrade to 7.6 we won't be needing <ProjectGuid> anymore?

[duncanp-sonar]

@jonathann92 unfortunately not. SQ7.6 is the minimum version of SQ that will be able to support projects with without ProjectGuids, but we still need to make some changes in the Scanner for MSBuild.

[jon-is-me]

@duncanp-sonar Sorry I had a typo in my above comment I put angle brackets around a word, I meant to say:
if we upgrade to 7.6 we won't be needing ProjectGuids anymore?

In your reply, what do you mean by support projects with ProjectGuids? I believe right now SQ6.7 requires ProjectGuids.

[duncanp-sonar]

...and I wrote "with" instead of "without"... I've edited my previous comment.

[lg2de]

@duncanp-sonar, what kind of changes are required in the Scanner?
I would like to support these changes!
We have started a project completely with .NETCore. Now we need the project GUIDs only for SQ. I would like to remove these GUIDs as soon as possible.

[hueidou]

Another solution is adding a .sln, then dotnet build solutionfile.sln instead of dotnet build projectfile.csproj, sonar-scanner will use the ProjectGuid in .sln.

[rickardp]

@huridou Yes, that was my second workaround in the original issue report. Hoping for the scanner to be fixed though, as msbuild doesn’t use projectguids anymore.

The sln file format is also a hopelessly outdated piece of legacy and its use of project guids is there basically to support the GUI only.
dotnet/msbuild#1730
If MS actually fixes this (maybe when VS code becomes the new VS?) the workaround wouldn’t work anymore. But that probably won’t happen in years.

[CodeSwimBikeRunner]

Is it possible to do a build off .csproj and the scanner work? What do we need to do to fix this?

[mkowalskigps]

Any updates on this given things are up to version 7.9?