Hydra vNext: New features

This topic will contain brief information about interesting new features, significant bugfixes and breaking changes in the next releases of Hydra.

New feature: Custom App.config support for .NET plugins loaded by Delphi hosts

Currently .NET plugins use default App.config file that should be bundled with the host .exe. This is a major issue in case App.config should contain assembly rebinding configuration (a very common case for projects using NuGet packages) or framework configuration (WCF / EF / etc). Main issue is that it was not possible to use different .config files for different plugins.

Starting next release the following approach will be used for App.config configuration files handling:

  • If a .NET plugin is loaded into a custom .NET domain and there is a file named [plugin assembly name].config (f.e. MyPlugin.dll.config) then this configuration file will be applied. Each .NET plugin loaded into a custom .NET domain can use its own App.config file

  • If a .NET plugin is loaded into the default .NET domain and there is a file named Hydra Global AppDomain.config then this configuration file will be applied. Note: Due to platform restrictions only one .config file can be used for the default .NET domain. So only one .config file will be applied.

  • If no custom App.config files are provided then the default .config file named [host exe name].config (f.e. DelphiHostapp.exe.config) will be used. This file should be placed next to the host .exe file. Its settings are applied to all plugins loaded by the host. Configuration is applied when the first .NET plugin is loaded and cannot be changed afterwards. This is the current behavior that remains unchanged.

1 Like