Introducing ReSharper 6.1 SDK

This post is about ReSharper 6.1. For other features in ReSharper 6 (both 6.0 and 6.1), please see previous posts introducing ReSharper 6. Those cover support for JavaScript (including unit testing with QUnit), CSS, ASP.NET MVC 3 Razor, and Async CTP; bundled decompiler; explanations on ReSharper inspections; fine-tuning file headers; ReSharper settings revised in 6.1 (and their company-wide usage); recent improvements in IntelliSense options, and optimizing assembly references

Though every new release of ReSharper comes with extra features and functionality, there are always things that our users want that don’t come out of the box. This includes things like, for example, support for various unit test frameworks as well as various bits of functionality that are domain-specific or related to particular challenges a user is facing.

Luckily, ReSharper has always shipped with an Open API which provided the opportunity to write plug-ins — extensions to the core ReSharper mechanisms that would be provided in separate files and integrated into ReSharper at start-up. While the opportunity was always there, and has resulted in a number of plug-ins being written, there’s never been any framework that would simplify the task for plug-in developers. Until now.

With the release of ReSharper 6.1, we have also introduced the ReSharper SDK — a separate framework that has been designed to make plug-in development easier. The SDK includes the following:

  • ReSharper assemblies, including PDBs and documentation XML files. These files include not just the core ReSharper assemblies, but also the unit test framework, which lets you write unit tests for your plug-in.
  • MSBuild target files, which make referencing the ReSharper assemblies a lot easier.
  • Project and item templates for VS2010, which make getting started with plug-in development a breeze.

Two packages are provided with the SDK: the MSI installer, which comes with all of the above, as well as a ZIP package, which contains only the assemblies and target files, and is provided to help build and test plug-ins in Continuous Integration systems such as TeamCity. Both packages contain introductory documentation to help you get started, with the bulk of documents related to plug-in development available online. These documents contain a variety of topics such as how to port your plug-in to use the SDK, develop support for a new language, or deploy the plug-in. The documents are being actively developed, and you’re welcome to comment on them should things start getting unclear.

The SDK packages are available on the ReSharper Downloads Page under Related Downloads. The following JetBrains TV video provides a comprehensive overview of the various SDK features including plug-in development, testing and configuration under TeamCity.

This entry was posted in How-To's and tagged , , , . Bookmark the permalink.

9 Responses to Introducing ReSharper 6.1 SDK

  1. Sven says:

    Thanks a lot for the hard work to finally get a SDK :)

  2. @Sven
    You’re very much welcome. We hope it serves its purpose well, and are willing to improve based on further feedback.

  3. Arno Nyhm says:

    I do not see the embedded video widget at the page with my iphone. Please add iphone support to your embedded videos

  4. @Arno
    We’re looking to do that in future. Thanks for emphasizing the demand for iPhone support )

  5. Andy says:

    Does the SDK works with R# Version 6.1.1 from the EAP?

  6. Dmitri says:

    @Andy: no, due to some internal restructuring, we’re currently not putting up SDK packages together with EAP builds. Expect this to be fixed in the near future.

  7. Bart says:


    You said the SDK would be fixed for EAP products.
    Is there an SDK available that van be used in combination with version 7.x ? Would be great !

  8. Joe White says:

    @Bart, every EAP build has a corresponding SDK build right next to it on the download page.

  9. Dmitri Nesteruk says:

    @Bart: yep, the SDK is available for download on this page, right next to ReSharper itself.

Leave a Reply to Dmitri Nesteruk Cancel reply

Your email address will not be published. Required fields are marked *