Installing ReSharper and the plugin into an experimental Visual Studio instance (hive) affects the following directories: Visual Studio / ReSharper Relevant Directories The runVisualStudio.ps1 script will always download the latest available installer for ReSharper - this can be either a normal release or early-access-program (EAP) releaseĪvailable versions are listed here for ReSharper and Rider (under ).The SdkVersion property in Plugin.props will affect the referenced NuGet package and will also determine the wave version that is required for the Extension Manager in ReSharper.The ProductVersion variable in adle is responsible for download a certain Rider frontend distribution.There are a couple of version identifiers that should always be updated synchronously: Opening the solution in Rider or IntelliJ IDEA will automatically provide the corresponding run configurations: Most importantly, to run and debug your plugin, invoke: This repository contains a few sample projects for various extension points:įor general development, there are a couple of scripts/invocations worth knowing. The only place that currently needs to be updated manually is the RIDER_PLUGIN_ID in README.md, which you'll only get after uploading your Rider plugin the first time. Metadata including project website, description, author and others should be entered in Plugin.props and plugins.xml.

With the -build-only -force, all the build-relevant files can be updated (some reverts are most likely necessary).

Passing -resharper-only will exclude all Rider related files. This will create a new folder with all the structure ready to go and all identifiers, like namespaces, ids and file names, replaced with MyAwesomePlugin. Dotnet new resharper-rider-plugin -name MyAwesomePlugin

Download rider resharper