Define plugins by name

To facilitate ease of use, you can define a plugin name and then use it in a form instead of specifying the name of the Dynamic link library (DLL), the class name, and the method name. These custom plugins are defined in the %DNADataRoot%\ADE\config\ADE\Plugins directory.

Although you can not alter baseline plugins, you can remove them by adding the .remove.xml suffix and saving the file in the %DNADataRoot% directory.

The following is a sample plugins file using custom plugins. You can find the code for this example in Plugin examples.

<?xml version="1.0" encoding="utf-8"?>

<ADEPlugInSchema xmlns=http://www.telvent.com/ADEPlugInSchema

xmlns:xsi="http://www.w3.org/2001/XMLSchemainstance"

xsi:schemaLocation="http://www.telvent.com/ADEPlugInSchema

ADEPlugInSchema.xsd">

<PlugIn

Name="SampleTreePlugIn"

Assembly="OASySDNA.ADE.SamplePlugIns"

Class="SampleTreePlugIn"

Method="AddToolbarButton"

PlugInType="TreeForm"

ApplyFieldRules="false" />

<PlugIn

Name="SampleFormPlugIn"

Assembly="OASySDNA.ADE.SamplePlugIns"

Class="SampleFormPlugIn"

Method="AddToolbarButton"

PlugInType="RowEditForm"

ApplyFieldRules="false" />

<PlugIn

Name="SampleFieldPlugIn"

Assembly="OASySDNA.ADE.SamplePlugIns"

Class="SampleFieldPlugIn"

Method="AddRule"

PlugInType="Field"

ApplyFieldRules="false" />

</ADEPlugInSchema>

For information on the attributes of the elements, refer to Extend functionality using plugins.

Changes made in plugins definitions are merged on the fly when the Advanced Database Editor (ADE) starts. However, you must:

• Ensure the files are properly distributed.

• Restart ADE to apply the changes.