# Scanning the build binaries

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

## Generating a session ID <a href="#generating-a-session-id" id="generating-a-session-id"></a>

Before running the build scan and tests, you need to create a session ID. The session ID is provided for each step to link them together as one complete cycle

{% code overflow="wrap" %}

```powershell
SL.DotNet config --appName "myApp" --branchName "master" --buildName $BUILD_VERSION --includeNamespace myNameSpace.* --buildSessionIdFile buildSessionId.txt --identifyMethodsByFqn
```

{% endcode %}

{% hint style="warning" %}
The above parameter `buildName`  should reflect a meaningful versioning of your service or application.\
\
In some cases, you can use timestamps as well, via commands like `$(date +"%y%m%d_%H%M")` (Linux) or `"%date:~10,4%%date:~4,2%%date:~7,2%_%time: =0:~0,4%"` (Windows CMD) or `$(Get-Date -Format "yyyyMMdd_HHmm")` (Powershell)&#x20;
{% endhint %}

## Scanning the binaries <a href="#scanning-the-binaries" id="scanning-the-binaries"></a>

Run the scan of your binaries using the SeaLights agent with the following command:

{% code overflow="wrap" %}

```
SL.DotNet scan --buildSessionIdFile buildSessionId.txt --binDir c:\path\to\binaries --ignoreGeneratedCode true
```

{% endcode %}

{% hint style="warning" %}
The `binDir` folder must contain all the project’s PDB files.
{% endhint %}

{% hint style="info" %}
See [command-reference](https://docs.sealights.io/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/.net-core-agent/command-reference "mention") for full parameter details
{% endhint %}