Home > Installation > How to install a particular DXCore plug-in

How to install a particular DXCore plug-in

March 17th, 2011

To install a particular DXCore plug-in you need to copy the plug-in dll into your plug-ins directory. Usually it looks similar to this path:

%userprofile%\Documents\DevExpress\IDE Tools\Community\PlugIns\

where “%userprofile%\Documents” is a path to the user Documents folder.

Once you copied the plug-in assembly, start Visual Studio and the plug-in will be loaded automatically by the DXCore. To see the overall list of plug-ins loaded you can use the Plug-In Manager options page inside the Options Dialog. Make sure that the plug-in you installed is listed in the Plug-In Manager and the state of the plug-in is “Loaded”. For example, if we install the KeyWatcher plug-in, it will appear in the list:

DXCore PlugIn Manager options page

If you don’t see the installed plug-in in the list, the Messages diagnostic tool window may have some clues. To open it, go to the DevExpress | Tool Windows | Diagnostics | Messages menu item. Navigate to the top of all diagnostic messages, expand the “Loading plugins…” item, find the “CR_KeyWatcher” plug-in and see the details of its load to find any clues:

DXCore Messages window with CodeRush KeyWatcher

Note that the diagnostic messages are not logged by default, you have to manually enable the logging on the Diagnostics | Message Log options page:

DXCore MessagesLog options page

Products: all
Versions: 10.2 and up
VS IDEs: any
Updated: Nov/29/2011
ID: T042

Similar Posts:

  1. September 29th, 2011 at 07:05 | #1

    Don’t forget that you must “unblock” the dll after you copy it to your plugin’s directory.

    from: http://code.google.com/p/dxcorecommunityplugins/wiki/InstallInstructions

    1. Extract the plugin DLL from the zip file you downloaded and save it in your community plugins folder.
    2. Right-click the plugin DLL, select “Properties,” and on the “General” tab, click the “Unblock” button. This is required to enable DXCore to properly execute the code in the plugin.
    3. Restart Visual Studio. The new plugin should be available.

  2. September 29th, 2011 at 07:14 | #2

    @ Jon von Gillern
    Thank you very much for the tip!