Does this library use ReflectionOnlyLoad when identifying assemblies to load? A quick search of the source tree seemed to suggest it doesn't.
With other libraries in the .net framework days, I experienced problems where merely searching for assemblies with a given class method signature would load the assembly into the process. Not only does that lock the file but IIRC it can mean unwanted static constructors get run. How does this library avoid such problems?
Does this library use ReflectionOnlyLoad when identifying assemblies to load? A quick search of the source tree seemed to suggest it doesn't.
With other libraries in the .net framework days, I experienced problems where merely searching for assemblies with a given class method signature would load the assembly into the process. Not only does that lock the file but IIRC it can mean unwanted static constructors get run. How does this library avoid such problems?