====== Shadow copy Plugins ======

eBiss 3 allows replacing Plugin Dlls iat runtime. 
This accelerates the cycle: Create DLL -> End all clients -> Stop service -> Copy DLL to plugins -> restart everything.
Now simply copy the new DLL into the eBiss Plugins directory which is no longer blocked due to the loading of the assemblies from another directory.
Then, select {{images:refresh.png?nolink}} **Activate Shadowcopy-Plugins** in the eBiss main Directory [[en:hauptmenue:wartung]] .
The new version is now being used both in the client and in the service.

{{:images:sign_warning.png?nolink|}}**Note:** this only applies to the client that is calling the command. The others continue with the old version.
This also has no effect if, for example, a mapping is already loaded. However, if you load it again, you now see the updated data type.

For the whole thing to work, you need to adjust settings in the .config files of server u. Client.
It is also important that this works only if no process is accessesing the plugins. That means that both the server, and all clients must be stopped in the config on ShadowCopy plugins.

===== Recommended configuration =====
{{:images:sign_warning.png?nolink|}}**Note: ** The configuration can be done with the[[en:ueberblick:installation:konfiguration:start| eBiss Configurator]].

**eBiss.WinClient.exe.config**
<code><add key="PluginManager.ShadowCopyDirectory" value="%TEMP%/__sc_eBiss/%eBiss.EbServerHost%_%eBiss.EbServerPort%" /></code>

This gives the eBiss client a local copy of the plugins. Adding the paths for host & Port, this setting should work well with several installed eBiss clients as long as they differ in the servername and Port.

**eBiss.Service.exe.config**

<code>
    <add key="PluginManager.ShadowCopyDirectory" value="./Plugins/__sc" />
    <add key="PluginManager.ShadowCopyArchiveDirectory" value="./Plugins/__sc/Archive" />
</code>

In this configuration, the server keeps the shadow copies directly in the plugins directory.

If the ** ShadowCopyArchiveDirectory ** is specified, old versions (which are DLLs in the shadow directory but are not loaded anymore) are automatically moved to the archive. (This allows for a history of old DLLs.)) If this option is not set(such as DLLs that are in the Shadow directory but are no longer loaded) are deprecated in the ** ShadowCopyDirectory **.

{{:images:sign_warning.png?nolink|}}**NOte for developers:** If you are in debugging and the process reloads DLLs, the VS display of the variable values does not work anymore.