Support multiple solution files for .NET projects during SAST Scanning
<!-- The first four sections: "Problem to solve", "Intended users", "User experience goal", and "Proposal", are strongly recommended, while the rest of the sections can be filled out during the problem validation or breakdown phase. However, keep in mind that providing complete and relevant information early helps our product team validate the problem and start working on a solution. --> ### Problem to solve Currently, when a .NET repository has multiple solution files (.sln), the SAST scanning job (Security Code Scan) will fail as it's not sure which solution file to execute. This will prevent .NET projects from completing a scan and detecting any vulnerabilities. ``` MSBUILD : error MSB1050: Specify which project or solution file to use because the folder "/builds/NETProject" contains more than one project or solution file. ``` <!-- What problem do we solve? Try to define the who/what/why of the opportunity as a user story. For example, "As a (who), I want (what), so I can (why/value)." --> ### Proposal Pass a variable to tell the scanner which solution file to execute. ``` security-code-scan: variables: NET_BUILD_PATH: - solution_one.sln - solution_two.sln ``` ### Links / references <!-- Label reminders - you should have one of each of the following labels if you can find the correct ones!
issue