where are project templates from R# 9.1 nuget package?

I installed the latest 9.1.20150331.211640 SDK nuget package at http://www.nuget.org/packages/JetBrains.ReSharper.SDK

I created a temp project in order to install this because I am looking for the item templates and samples in order to get started.

this article seems to say that the nuget package only installs the reference assemblies and that there should be a MSI install that contains all the samples and templates

however, this article only applies to 8.1.

I also found a list of MSI install packages at

but this only goes up to 8.2

Any advice on where I can get the samples?


Comment actions Permalink

So at this point, I am assuming that the samples and templates are not yet ported to 9. so I am working on the 8.2 templates and samples and porting them instead.

Have to say, hardly any cohesive documentation on resharper plugin development. I'm starting to dig through existing 9.0 compatible plugins that are open source to get some clues but a sample nuspec wouldnt hurt or a walkthrough for an easy plugin.

My end goal is to do a custom language plugin and not sure if I am opening myself up for a world of hurt. I'm sure I can science out the various stopping points but the time it will take to get all the way to the finish line worries me a bit.

Comment actions Permalink

The samples aren't available for 9.0/9.1 yet, I'll be updating them and putting them on github as part of the 9.1 release. We're not going to be updating the templates - they became very basic once we switched to nuget packages. Instead, just create a Class Library and add a reference to JetBrains.ReSharper.SDK. Make sure you take a look at the devguide for lots of details on plugin development: https://www.jetbrains.com/resharper/devguide

Comment actions Permalink

I've been absolutely scouring the dev guide over the last week or so. The biggest issue is that there is a lot of conflicting information. Much of it is written from the 8.2 perspective in terms of how to create your nuget packages as well as how to launch your plugin, and it's hard to distinguish which is the correct information if you are new to plugin development. In fact, the devguide states that the sdk comes with samples and project templates.

the other big issue is that the information is fairly spread out. I've read the first few sections of the dev guide at least 6 times and each time I get a new piece of information. many times I get the new piece of information after I've already learned the lesson the hardway by banging my head against the code for a while. in fact, after learning the hard way about the namespace refactoring by scouring the assemblies, I finally digested the sentence in the dev guide that talks about that.

There are also a lot of holes in the documentation and there are almost no sample projects that use the 9.x SDK. I scoured github and found versions of zenSharp and angularJS but there is no way to find them through the documentation (unless I havent digested those sections either )

There is no API which makes things very hard. I saw your other post where you say that developing plugins is much better served by not having an API and forcing people to rely only on the assemblies but not many developers have that deep of knowledge of .NET to efficiently do that. Some kind of blog post on your development process and tools for efficiently doing this would go a really long way. And it's a pretty tall order to ask people to have to disassemble resharper and all it's tools in order to get a handle on API that they dont see directly used in sample code.

An API reference of the classes that are most frequently used would be very helpful, it's one thing to just see a function being used and guessing what it does or having to trace through all its usages in order to get a handle on how it's used (or even finding the classes you want to use for that matter), it's a completely different world if we had a way to browse the packages with lists of namespaces, classes, and methods even if it doesnt have actual documentation. at least we could easily see what was in the API and potentially search for things that we then later scan the asemblies for how it's used.  

All these elements combined, this makes for a pretty difficult experience in expanding your platform. It's a much more difficult expereince than creating plugins for any of the other intellij based platforms.

The ability to add a simple action in resharper should be easy to do.


Please sign in to leave a comment.