Fortify VSTS Plugin always defaults to Debug Build for SCA
I'm currently using the Fortify VSTS Plugin to perform automated Fortify scans on .NET applications as part of our build process using the Fortify Static Code Analyzer Assessment task and I've noticed that when SCA executes devenv.exe to build the application it always elects to use the DEBUG build configuration by passing that as one of the command line arguements.
I was wondering if we have control over which build configuration it uses or is it automatically set to use the DEBUG build by design?
Re: Fortify VSTS Plugin always defaults to Debug Build for SCA
The debug build is necessary in order for SCA to run a full scan. This is why the debug is added to the commandline. Even if possible you should not change that.