Skip to content

Releases: SonarSource/sonar-scanner-msbuild

4.4

03 Oct 11:00
a8f0b1c

Choose a tag to compare

4.4

New Features

  • #561 - Report all Roslyn issues to SonarQube/SonarCloud

Improvements

  • #543 - Setting sonar.verbose=true should set sonar-scanner-cli's debug mode

4.3.1

14 Jun 12:40
33b3d0a

Choose a tag to compare

New Features

  • #417 - Publish as a .NET Core Global Tool

4.3

04 Jun 16:35

Choose a tag to compare

4.3

Improvements

  • #477 - Scanner should not suggest to use -X
  • #491 - "sonar.msbuild.testProjectPattern" should have a default value
  • #498 - Scanner for MSBuild .Net Core should be available as a chocolatey package
  • #502 - Error message for unsupported versions of MSBuild can be misleading
  • #506 - Rename chocolatey package key
  • #509 - Digitally sign binaries to not be blacklisted by antivirus
  • #522 - Break the build when running under local system account

Bug fixes

  • #455 - Argument null exception when there are no active rules in the chosen quality profile
  • #513 - Build fail with scanner for msbuild when OutputPath property of WPF project contains $(MSBuildProjectName)

Won't fix

  • #448 - Analysis may fail on concurrent builds

4.2

18 Apr 09:34

Choose a tag to compare

4.2

Highlights

  • This release allows to support analysis of more of the default msbuild projects

Improvements

  • #446 - Support more msbuild project types
  • #463 - Add support for analyzing more sql files
  • #470 - Allow users to simply extend the list MSBuild Project Items

Bug fixes

  • #459 - User-Agent header is sent only on requests to /api/server/version

4.1.1

22 Mar 16:49

Choose a tag to compare

Bug fixes

Fix bug when trying to find CodeCoverage.exe using registry

4.1.0.1148

15 Mar 15:25
c841143

Choose a tag to compare

Highlights

  • This release introduces a new, dotnet core-based Scanner for MSBuild. It is a cross-platform implementation that does not require Mono.

Bug fixes

  • SONARMSBRU-199 - Analysis should not fail for valid Windows file/folder names, e.g. containing commas
  • SONARMSBRU-339 - Scanner for MSBuild through VSTS extension no longer imports coveragexml
  • SONARMSBRU-366 - Legacy bootstrapper exe always returns exit code 0
  • SONARMSBRU-379 - GUID detection mechanism doesn't work properly with relative paths

Improvements

  • SONARMSBRU-231 - Test results should be uploaded automatically for VSTS builds
  • SONARMSBRU-327 - Consider failing the analysis when encountering projects with duplicate Guids
  • SONARMSBRU-360 - Analysing projects using "dotnet build /t:rebuild" does not work
  • SONARMSBRU-364 - Set User-Agent in HTTP requests
  • SONARMSBRU-367 - On private project scanner fails with "Forbidden" if "Browse" permission is missing
  • SONARMSBRU-374 - Log warning when the user running the build is local system and not a normal Windows user
  • SONARMSBRU-375 - Ensure all path comparisons within the scanner are done using OS-specific case and separator sensitivity
  • SONARMSBRU-376 - Fail the build is ImportBefore targets detect unsupported version of MSBuild
  • SONARMSBRU-377 - Dump sonar-project.properties (without sensitive data) into the logs when sonar.debug=true is set
  • SONARMSBRU-378 - Credentials must be passed in both begin and end steps or not at all
  • SONARMSBRU-380 - End step should display a clear message when one of the project doesn't have a GUID
  • SONARMSBRU-382 - Embed Sonar CLI Scanner 3.1.0.1141

4.0.2.892

20 Dec 13:17

Choose a tag to compare

Fixes cross-platform execution

4.0.1.883

18 Dec 15:30

Choose a tag to compare

Store analysis results in unique folders
Enable consistent metrics reporting
Fix sonar.projectBaseDir property
Fix various other issues

Release Notes

4.0.0.821

08 Dec 14:13

Choose a tag to compare

Added support for .Net Core multi-platform projects
Added support for running the scanner on non-Windows platforms

Dropped support for execution of FxCop

Release notes

3.1-beta.1

22 Sep 12:07

Choose a tag to compare

This beta release is meant to provide the artifact calling the .sh script in the case of a non-Windows based OS.

See this GoogleGroup thread