Scanning the build binaries

Create a build session ID and scan your .NET binaries before running tests.

The SeaLights .NET agent can scan the binaries after the build process to gather the build structure.

The examples below assume you downloaded the self-contained agent into ./sl-dotnet-agent. If you use a framework-dependent package, prefix the command with dotnet.

Generating a session ID

Before running the scan and tests, create a session ID. Use the same session ID across the full build and test cycle.

--buildName should reflect a meaningful version for the artifact you deploy.

PowerShell

.\sl-dotnet-agent\SL.DotNet.exe config --appName "my-app" --branchName "main" --buildName "$(Get-Date -Format 'yyyyMMdd_HHmm')" --includeNamespace "MyCompany.*" --buildSessionIdFile buildSessionId.txt --identifyMethodsByFqn

Azure DevOps

Bash

GitHub Actions

Scanning the binaries

Run the scan after the build completes.

PowerShell

.\sl-dotnet-agent\SL.DotNet.exe scan --buildSessionIdFile buildSessionId.txt --scanDir "C:\path\to\binaries" --ignoreGeneratedCode true

Azure DevOps

Bash

GitHub Actions

The scanDir folder must contain all the project’s PDB files.

See Command Reference for full parameter details.