5.6.7

• sln were not analyzed by standalone tool fix by @matteo-tosi in https://github.com/security-code-scan/security-code-scan/pull/262
• added --sdk-path parameter

Full Changelog: https://github.com/security-code-scan/security-code-scan/compare/5.6.6...5.6.7

5.6.6

• Fixed #258 "Standalone scanner throws exception: 'ProjectName' is already part of the workspace"

5.6.5

• Fixed #257 "Exception on solution that contains a Solution Items section"

Release Notes

5.6.4

• Support running dotnet tool against a single project
• Better filtering by projects in the dotnet tool
• #246 Package security-scan is not compatible with netcoreapp3.1

Release Notes

5.6.3

• #248 Be able to exit with non-zero error code when warnings are found

Release Notes

5.6.2

• Blue-yellow edition in support of Ukraine.

Release Notes

5.6.1

• Fixed #239 "Adding custom sanitizers to a config file in stand-alone runner".

Release Notes

5.6.0

• Added support for .NET 6.0 and VS2022

Release Notes

5.2.1

• New parameter --ignore-msbuild-errors for standalone runner to ignore errors from incompatible projects.
• Bug fixes and improvements.

Release Notes

5.1.0

• Standalone runner improved. My favorite way to run SCS!
• Bug fixes and improvements.
• A script was made by Sebastien gioria for importing the analysis results into DefectDojo.