Configure Project Settings for Veracode Static for Visual Studio
This topic is for the new Veracode Static for Visual Studio released April 2022. For the legacy versions of Veracode Static for Visual Studio, see Veracode Static for Visual Studio (Legacy).
You use the Veracode Project Settings Wizard to connect the Veracode application with the currently open solution and to configure these required files:
veracode-project.json, which is in the root of the solution directory and checked into source
veracode-project-user.json, which is in the same directory as the Veracode API credentials file:
veracode-project.json file does not exist when you start a scan, the wizard below opens to automatically create the project settings files for you.
The first step in the wizard is to select the Veracode application to connect to this solution. Just type any part of the Veracode application name into the entry field and click on the name of the application.
If you intend to run most of your scans in a sandbox, you can select the I want to scan in a development sandbox option, and then select the sandbox for your default scan. You can select a different sandbox or a policy scan at any time through the Custom Workflow window, so you are not locked into any scan type with your choice here.
After you select your Veracode application and optional sandbox, you see an example of the
veracode-project.json file you are about to create. By default, all build output is stored in a
.veracode/build directory in the solution directory.
.veracode directory in your solution folder is intended to be added to your
.gitignore file, so that you do not check it in to source control.
As mentioned elsewhere, the
veracode-project-user.json file is created in the same directory as the Veracode API credentials:
For full control of these settings, if they are only relevant to your scans, you can make additional entries in this file. These entries override the settings in the
Depending on your selection, after the wizard closes, either the scan starts or the Custom Workflow tool window opens.