This document describes the tehnical and legal limitations of DlhSoft component library licensing.
By purchasing a DlhSoft component library development license:
You are not allowed to develop and distribute your own component library products (targetted to developers) referencing DlhSoft libraries internally. You are allowed to develop such component libraries only for your own reuse in order to be able to develop applications (executable targetted project outputs) more easily. Technically, because DlhSoft uses the standard Microsoft® .NET licensing mechanism, the DlhSoft license files cannot be compiled and hosted within an output library assembly (DLL file). They can obly be stored within a .NET executable assembly (EXE file). As a consequence, even if you need to develop plug-ins for some third party applications such as Microsoft® Dynamics®/Navision, or controls to be consumed as objects in a .NET or COM/ActiveX-based environment, these technical limitations would apply. In these cases, provided that your code will not be reused by third party developers, but used only directly by end-users (by installing your plug-in or by adding your control to their application environment at runtime), you will need to purchase a Business Plus license for the DlhSoft product, in order to use the original DlhSoft source code (available only as a benefit of that license type) to build your own component assemblies, without enforcing the standard .NET licensing mechanism.
Alternatively, to set a DlhSoft license for specific client components used in applications hosted in an environment that doesn't support resource-based licensing, developers need to call a static method at application initialization time (before creating component instances), providing the license file content as a string parameter:
[Namespace].Licensing.[ComponentName].SetLicense("[...]");