Using the latest JFrog products?
JFrog Platform User Guide

Skip to end of metadata
Go to start of metadata


The JFrog Visual Studio Extension adds JFrog Xray scanning of NuGet project dependencies to your Visual Studio IDE. It allows developers to view panels displaying vulnerability information about the components and their dependencies directly in Visual Studio. With this information, a developer can make an informed decision on whether to use a component or not before it gets entrenched into the organization’s product.

The extension filter allows you view the scanned results according to issues severity.

Source Code

The JFrog IDEA Plugin code is available on Github.

Page contents

Installation and Setup


  • Visual Studio 2017.
  • JFrog Xray version 2.5.0 and above.


To install and work with the extension:

  1. Open the terminal and type nuget. If it is not recognised as a command, please add nuget.exe to the PATH environment variable.
  2. Open Visual Studio
  3. Go to Tools | Extensions and Updates
  4. Search for JFrog.
  5. Click on Download
  6. Once the installation is completed, re-open Visual Studio.

Configuring the Extension to Connect to JFrog Xray

Once the extension is successfully installed, connect Visual Studio to your instance of JFrog Xray.

  1. Go to Tools | Options | JFrog | JFrog Xray 
  2. Set your JFrog Xray URL and login credentials.
  3. Test your connection to Xray using the Test connection button.

Using the Extension

Scanning and Viewing the Results

To scan and view the project dependencies, open View | Other Windows | JFrog

JFrog Xray automatically performs a scan when the project is opened or when clicking on the Refresh button in the JFrog window.

Filtering the Scanned Results

The JFrog Extension provides a filter to narrow down the scanned results to view exactly what you need.


When troubleshooting issues, it os recommended to look at the log messages in the Output console, located at the bottom of the screen.

Reporting Issues

Please report issues by opening an issue on Github.

Release Notes

The release notes are available on Bintray.

Watch the Screencast


  • No labels