I would like to load a specific ConfigurationSection but the way the CLR loads the assemblies is giving me some trouble:
My CustomConfigurationSection definition is on a specific assembly which cannot be found by the overall process of assembly loading, because I'm using an external tool which basically loads my assembly, discovers some information about it via reflection and then tries to "install" it. Very much like the installutil when trying to install a windows service.
I'm going nuts because the ConfigurationManager tries to find the required assembly for my ConfigurationSection under the location of the original process. I know this for sure as I'm using SysInternals Process Monitor. Can someone provide some workaround or directions?
Thanks!