AdaskoTheBeAsT.SecurityCodeScan.VS2022 5.6.7.31

dotnet add package AdaskoTheBeAsT.SecurityCodeScan.VS2022 --version 5.6.7.31                
NuGet\Install-Package AdaskoTheBeAsT.SecurityCodeScan.VS2022 -Version 5.6.7.31                
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="AdaskoTheBeAsT.SecurityCodeScan.VS2022" Version="5.6.7.31">
  <PrivateAssets>all</PrivateAssets>
  <IncludeAssets>runtime; build; native; contentfiles; analyzers</IncludeAssets>
</PackageReference>                
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add AdaskoTheBeAsT.SecurityCodeScan.VS2022 --version 5.6.7.31                
#r "nuget: AdaskoTheBeAsT.SecurityCodeScan.VS2022, 5.6.7.31"                
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install AdaskoTheBeAsT.SecurityCodeScan.VS2022 as a Cake Addin
#addin nuget:?package=AdaskoTheBeAsT.SecurityCodeScan.VS2022&version=5.6.7.31

// Install AdaskoTheBeAsT.SecurityCodeScan.VS2022 as a Cake Tool
#tool nuget:?package=AdaskoTheBeAsT.SecurityCodeScan.VS2022&version=5.6.7.31                

Security Code Scan
Vulnerability Patterns Detector for C# and VB.NET - Website

Build

Downloading

Official releases are available as nuget package, Visual Studio extension and stand-alone runner.

Building

git clone https://github.com/security-code-scan/security-code-scan.git
cd security-code-scan

Open SecurityCodeScan.sln in Visual Studio or build from command line:

nuget restore SecurityCodeScan.sln
msbuild SecurityCodeScan.sln

Contributing

Tests

Most of the tests are written in two languages: C# and VB.NET. If you aren't an expert in VB.NET (me neither) use any online converter to create the VB.NET counterpart from tested C# code example.
Tests are ideal for developing features and fixing bugs as it is easy to debug.

Debugging

In case you are not sure what is wrong or you see AD0001 error with an exception, it is possible to debug the analysis of problematic Visual Studio solution.

Visual Studio offloads some static analysis work to a separate process. It is a good idea to uncomment the lines to have a chance to debug the child process.

First, make sure there are no Security Code Scan Visual Studio extensions installed to avoid interference.
Right click SecurityCodeScan.Vsix project in the solution and choose Set as StartUp project.
Start debugging in Visual Studio. It will open another instance of Visual Studio with debugger attached.
Open the solution with the problematic source.

There are no supported framework assets in this package.

Learn more about Target Frameworks and .NET Standard.

  • .NETStandard 2.0

    • No dependencies.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.