Archive

Archive for the ‘DXCore’ Category

DXCore Components – ContextPicker

September 25th, 2010 Comments off

The ContextPicker component allows users to specify sophisticated context expressions. It is populated from the context providers registered in the DXCore. For example, take a look at the Shortcuts options page and the context picker used on this page where you can bind a context for any shortcut available.

Read more…

DXCore Components – ContextProvider

September 25th, 2010 Comments off

The ContextProvider component provides a new context entry for the ContextPicker component. Context is automatically registered in the DXCore when a plug-in containing the corresponding ContextProvider is loaded.

You can drop the ContextProvider onto your plug-in design surface from the “DXCore: Extensions & Providers” category of Visual Studio Toolbox:

Read more…

How to programmatically verify a context

September 25th, 2010 Comments off

Here’s a sample code of how to programmatically verify a particular context inside of your DXCore plug-in. You may achieve this using the Context service like this:

CSharp code:

ContextResult result = CodeRush.Context.Satisfied(@"Focus\Documents\Source\Code Editor");
bool editorHasFocus = result == ContextResult.Satisfied;

Read more…

How to add a button to the DXCore Visualize toolbar

September 17th, 2010 Comments off

To place a new button on the DXCore Visualize toolbar, all you need to do is to add a new DXCore Action component on your plug-in design surface, and adjust its ToolbarItem properties group:

Read more…

DXCore Components – Action

September 17th, 2010 Comments off

The Action component is one of the primary, simplest and useful components of the DXCore. It registers an “action” within DXCore/CodeRush and the Visual Studio IDE, which can be triggered using either a keyboard shortcut or a mouse button (with the shift key if necessary), and/or placed within a Visual Studio menu (e.g. in the IDE main menu, Code Editor context menu, etc).

Read more…

DevExpress DXCore controls overview

September 14th, 2010 2 comments

DXCore contains uniquely-named duplicates (to avoid naming collision and other design-time issues) of most of DevExpress controls. These controls are located in the “DevExpress.DXCore.Controls.*” assemblies. They can be used when writing DXCore plug-ins only. It is impossible to use these controls in an arbitrary application. You need the DXCore design-time assemblies to be able to use these components at design time. However, these assemblies are only available for customers who have a DXperience Subscription (customers who have already paid for the design-time portion for the corresponding controls in DXCore).

Also, there are several other DXCore-specific components added into your Visual Studio toolbox, which you can use inside your DXCore based plug-ins.

—–
Products: DXCore
Versions: all
VS IDEs: any
Updated: Dec/28/2010
ID: D008

How to add support for dropping markers into CodeRush Xpress

September 3rd, 2010 Comments off

CodeRush Pro has great Markers support, but, unfortunately, CodeRush Xpress lacks it – you can’t drop them manually using the Alt+Home shortcut. Here’s an example of how you can work around this limitation.

1. Create a new DXCore plug-in via the File -> New -> Project… -> Visual C# -> DXCore -> Standard Plug-in item. Enter a name of the plug-in if necessary and click OK:

Read more…

How DXCore plug-ins are loaded

August 19th, 2010 2 comments

DXCore has a built-in Loader Engine, which is intended to improve the speed of its start-up process. However, the first DXCore start-up process is pretty long (it may take a minute or two). There’s a reason that the first start-up takes much more time then the subsequent launches. When DXCore loads for the first time, it has to load all of the plug-ins found in both, “System” and “PlugIns” subfolders. At this time, DXCore profiles every loaded assembly: checks its load type, loading time, so in brief, all important and necessary information that DXCore should know about a particular assembly. All this information is saved to Loader profiles in an XML format. This information will be used on every subsequent DXCore launch, so that Visual Studio should start instantly, because, in the first place, plug-ins are loaded from profiles only after the splash screen goes away and, secondly, because Loader Engine has optimized DXCore loading process specially for your system.

Read more…