Since version 2.6, EPLAN API assemblies are shadow copied, i.e. during registration, they are stored into a temporary folder, and loaded from there (See API Help: "Shadow Copying API Assemblies").

This concerns both add-ons and add-ins.

For add-ons, the entire bin directory of the add-on with subdirectories is copied to the user application roaming directory (%appdata%\EPLAN\ShadowCopyAssemblies\Process-ID\Addon-Name). 

Example:

 

 

So all files (*.dlls  and  *.exe) and all  bin  subdirectories (language subdirectories etc.) are also copied. This is done when EPLAN starts and an add-on is registered or when an add-on is manually registered from the Add-ons dialog. 

EPLAN will load the assemblies of the add-on from the shadow directory and not from the original add-on directory. This means that an add-on can be updated without having to stop all EPLAN instances that use the add-on.

 

What EPLAN does ?

At any start of EPLAN, the registry or the path for server add-ons is scanned for new add-ons. The  install.xml  is read and the following things are done:

• Does this add-on fit to the main version?

• Is the correct license option booked?

• Is the version correct?

When everything is done so far, EPLAN then registers the new add-on:

• Read all  *.xml  files from the  CFG  folder. The settings are copied to the settings of the main version.

• Read the  eplset<applicationmodifer>.xml: All binaries defined there are loaded now.

• Load the API modules.

• Register the API references.

• Register the scripts.

• Copy the base data of the add-on to the base data of EPLAN.