Archive

Posts Tagged ‘DXCore Objects’

How to use DXCore DecoupledStorage to persist plug-in data

December 16th, 2010 Comments off

To persist your data using the DecoupedStorage object, use the appropriate ReadXXX and WriteXXX methods. In case your settings are language dependant, DecoupledStorage includes a property “LanguageID” that can create and select child storage objects for the purposes of language-specific storage (e.g., to support independent settings for C#, C++, Basic, etc.). Just set the LanguageID to the appropriate Language identifier (e.g., “CSharp”, “C/C++”, “Basic”, etc.), and then read and write normally. To activate the language-neutral storage object, set the LanguageID to an empty string. If your code is inside a CodeRush Options Page, you can get the LanguageID through the Options page’s LanguageID property (also, you can handle the LanguageChanged event in your Options page to find out when the user wants to create settings for another programming language).

Read more…

DXCore DecoupledStorage structure and settings file format

December 16th, 2010 Comments off

The DecoupledStorage object is used to handle storage for your DXCore plug-ins data. Usually, DecoupledStorage represents a single DXCore Options Page. If you are not going to create an Options Page, the DecoupledStorage will represent just named data storage.

The storage has three main identifiers (properties):

  • Category (i.e. the path to the storage)
  • Name (e.g. “MyPlugIn Settings”)
  • Language (e.g. C#, C++, VisualBasic)

Read more…

DXCore DecoupledStorage object for storing data

December 16th, 2010 Comments off

As the name says, the object handles decoupled storage for DXCore plug-ins. It is recommended for plug-in developers to use DecoupledStorage for persisting data (e.g. plug-in settings). The storage has its own structure and saved in a file of a specific format in the appropriate location.

Read more…