'TimeSpan' is an ambiguous reference between 'System.TimeSpan' and 'System.TimeSpan'

[patrick.elmore]

@Andrei_Epure It will take a some time to do some of the troubleshooting steps requested, but here is the info you requested I can give you right away.

@Andrei_Epure

2022-02-17 13:34:10 UTC - this is when sonar-security-csharp-frontend-plugin-9.4.0-M1.15235.jar was deployed. This is used for our security offering. @patrick.elmore Do you have a way to verify if the issues started to occur after this date?

The first occurrence of the issue was February 17, 18:30 UTC. The build prior to the that was successful, and it ran on February 16, 16:43 UTC.

@Andrei_Epure

On 2022-02-15, Visual Studio 2022 version 17.1.0 got released, and this is what you are using: MSBuild version = "17.1.0+ae57d105c" . Was the last successful build using a previous version, i.e 17.0.0?

We have failed builds using two versions of the windows-2022 VM image. On has MSBuild 17.0.x, the other has 17.1.x. Images in question 20220207.1 and 20220227.1.

@Andrei_Epure

Regarding the possibility that this issue started manifesting itself with MSB 17.1.0 :

• If you use the previous version of VS2022 in your CI, will it work?

Based on the VM image information above, this does not appear to be a direct result of MSBuild 17.1

@Andrei_Epure

If using VS 2022 17.0.0 doesn’t fix the issue, could you exclude the project that fails from the analysis, as a temporary mitigation and to unblock your pipelines?

<PropertyGroup>
  <!-- Exclude the project from analysis -->
  <SonarQubeExclude>true</SonarQubeExclude>
</PropertyGroup>

We had come across this in another unrelated thread and attempted adding it to the project in question. The issue continued to persist.

@Andrei_Epure

Can you reproduce it locally with 17.1.0? If yes, can you share the repro project with us (privately if needed)?

I have not run dotnet-scanner locally, but I will give it a try and post the results once complete.