DXCore Text Commands overall list
Here is the list of text commands provided by the DXCore Framework.
Here is the list of text commands provided by the DXCore Framework.
Here is a sample code illustrating how to detect if the DXCore is installed and loaded from another add-in (without static dependencies on the DXCore assemblies) using reflection. This could be helpful if your add-in functionality somehow intersects with the DXCore’s.
From inside a usual DXCore plug-in, you can detect if the DXCore is loaded by calling the “CodeRush.IsLoaded” property. In case you are not going to reference the DXCore assemblies inside your add-in, this sample might help.
Here is a list of terms often used when talking about IDE tools (including CodeRush, DXCore and Refactor!) for a better understanding of these products. The list is not complete and it is going to be updated from time to time.
Actions associate a name with functionality, which can be triggered using either a keyboard shortcut or a mouse button, and/or placed within a Visual Studio menu. Some actions accept parameters that can change their behavior.
Action hints inform new users about IDE tools features, as they occur by pointing to a location on-screen with a large colored arrow, displaying a short text message.
The CodeRush object provides access to DXCore/CodeRush services. Historically it was called CodeRush, because DXCore framework was not decoupled from the CodeRush product at the beginning; in other words, DXCore did not exist at that time. Today, it should technically be called DXCore.
The full list of services accessible through CodeRush object can be seen in the corresponding topic.
If you’d like to show your tool window from a DXCore-based ToolWindow plug-in, you have to create another standard plug-in that will do this. You can add an additional DXCore standard plug-in project item into your solution, where the tool window is located. In the new plug-in, you need to handle the DXCoreLoaded event and manually add a code that opens and shows a tool window.
Here is the list of services (and a few properties) DevExpress DXCore provides, which are accessible through the main CodeRush object:
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.
DXCore has two types of plug-ins. They are “System” and “Ordinary” plug-ins. System plug-ins are located in the similar “System” folder, and all other plug-ins (usual or user plug-ins) reside in the “PlugIns” folder. These folders are located in the “Bin” folder of every product installed. The difference between “System” and ordinary plug-ins is that the former are always loaded before all other plug-ins.