Dynamic Assembly Loading
Dynamic assembly loading is the mechanism that discovers new BPUA functionality at runtime. It is used during initial platform boot and again during on-demand use case activation.
AssemblyLoadingProcessConfigurator - loads configuration and calculates the plugin root path.DynamicAssembliesLoader - loads assemblies from a physical folder.BPUAServiceAssemblyProcessor - examines loaded assemblies and registers discoverable services.BPUAServicesRegistrar - resolves service keys and registers service types into the registry.AssemblyTypesLoader - safely enumerates assembly types even when full type loading fails.Loading a DLL is only the first step. The platform must then answer additional questions:
That is why the loading pipeline includes processors and registrars rather than stopping at physical assembly loading.
The plugin root is taken from the PluginFolder setting in configuration.
In development mode, the path can be treated differently from production mode, allowing the same runtime logic to work
both from source-oriented and deployment-oriented folder layouts.
Dynamic assembly loading is the extensibility backbone of the platform. It is how BPUA turns an abstract plugin architecture into a concrete runtime discovery mechanism.
Table of Content BPUA Chapter Previous: Use Case Assemblies Next: UseCaseActivator
Business Process Programming in .Net
© 2004-2026 Laskarzhevsky Software Inc.
Unless otherwise noted, the content of this website is licensed under the
Creative Commons Attribution 4.0 International License (CC BY 4.0).
Code examples are provided under the MIT License.
You are free to share and adapt the material provided that appropriate
credit is given and any modifications are clearly indicated.
The information provided on this website is for educational purposes only.
The author and publisher make no warranties regarding the completeness
or suitability of the information and are not responsible for any damages
resulting from its use.