Run an analysis with Visual Studio extension
Last updated
Was this helpful?
Last updated
Was this helpful?
Open your solution and run Snyk scan. Depending on the size of your solution and the time needed to build a dependency graph, it takes less than one or two minutes to get the vulnerabilities.
The extension provides two kinds of results:
Open Source vulnerabilities
Snyk Code issues
Note that your solution must be built successfully in order to allow the CLI to pick up the dependencies and find the vulnerabilities.
If you see only npm vulnerabilities or vulnerabilities that are not related to your C#/.NET Projects, that can mean your Project was not built successfully and was not detected by the CLI. If you have difficulty or questions, submit a request to Snyk Support.
Snyk Code analysis shows a list of security vulnerabilities and code issues found in the application code. For more details and examples of how others fixed the issue, select a security vulnerability or a code security issue and examine the suggestions that Snyk provides.
The suggestions from Snyk include the recommendation of the Snyk engine using, for example, variable names in your code and the line numbers in red. You can also see:
Links to external resources that explain the bug pattern in more detail.
Tags that were assigned by Snyk, such as Security (the issue found is a security issue), Database (the issue is related to database interaction), or In Test (the issue is within the test code).
Code from open-source repositories that can be of help to see how others have fixed the issue.
For projects using Git repositories, Snyk can filter the displayed issues to show only issues introduced in the working branch.
To do this, Net New Issue Scanning must be enabled under Scan Configurations in the Extension Configuration.
First, scan the reference branch selected in the Snyk view, for example, git master
or main
.
Second, scan the working branch.
Then calculate the difference between both and display only the difference
The following are the steps to choose ther reference branch:
Click the Project node to open the branch chooser dialog.
Choose the branch that is the reference against which new issues shall be calculated
Continue by running a scan on your working directory.