1

I wrote a Resharper plugin that seems to only work when users have the Resharper SDK installed. Is there a way to package the required libraries into the plugin dll, so that users just need to drop the dll in their Resharper Plugin directory for Visual Studio to recognize it?

Matthew Piziak
  • 3,430
  • 4
  • 35
  • 49
  • Is it necessary to package as a single dll? If so, ILMerge.exe might help you package any dependencies into your dll. Here's different technique to the same end: http://blogs.msdn.com/b/microsoft_press/archive/2010/02/03/jeffrey-richter-excerpt-2-from-clr-via-c-third-edition.aspx, which seems like the nifiest way to package in the missing libraries. – spender Jul 12 '12 at 15:11

2 Answers2

4

You don't need to package the libraries, only your plugin. If it's not working, check it on the Plugins options page, see if it's loaded. There's a developer log link on the bottom of the page.

Dmitri Nesteruk
  • 23,067
  • 22
  • 97
  • 166
  • After further examination, it seems that the plugin is recognized, but the ContextAction only works when they build the dll themselves. Do you have any idea why that might be the case? – Matthew Piziak Jul 13 '12 at 15:46
  • Matthew, I don't know, can I take a look at your source code? – Dmitri Nesteruk Jul 13 '12 at 20:26
  • 1
    Dmitri helped me with my issue - it turned out to be quite unrelated to ReSharper. The users of my dll simply had to unblock the dll before using it, via Properties -> Unblock. – Matthew Piziak Jul 17 '12 at 12:40
-2

This may not be a solution to exactly your problem, but within the "References" virtual folder in the project, if you go to properties to one of the references you have the property of "Copy Local", which will copy the DLL to the output directory. If you do this for all references that come from the SDK, it might work.

I did this for a web server that didn't have asp.net MVC installed, yet my project was.

EDIT: Set the property to true

Matthew
  • 24,703
  • 9
  • 76
  • 110