Ensure dynamically loaded assemblies for client controls are imported

When the primary client control assembly is imported into the galaxy during an application’s deployment, all statically-linked dependent assemblies are identified and imported into the galaxy as well. However, if the client control contains dynamically loaded assemblies, these assemblies are not automatically loaded in the galaxy.

There are two methods for ensuring that the client control’s dynamically loaded assemblies are included in the galaxy when the primary assembly is imported:

• By including the list of dynamically loaded assemblies in an XML manifest resource that is embedded in the primary assembly. The advantage of this method is that the required configuration information is packaged with the assembly, so no any other packing mechanism is required.

• By including the list of dynamically loaded assemblies in an external XML configuration file that is stored in the same directory as the primary assembly.

  Note: Both methods can be used simultaneously to provide redundancy, in the event that one of the dynamically loaded assembly lists is missing a required assembly.