14th April 07:33
Loading DLLs App.config from alternate location
DLLs do not have config files, confile files are for *applications*
NO! Do not do this. It is deprecated in v2.0. Even in 1.1 it is buggy.
Well, the company policy is wrong: tell your boss that. .NET requires
that private assemblies without a strong name are under the application
folder (bin, in your scheme). They can be in a subfolder (eg bin/dll)
which can be set through the config file. Libraries with a strong name
can be located anywhere on the machine (or anywhere on the internet),
but you can only do this for a specific version of the library, and this makes things messy.
The default location is the application folder, and as John's mentioned,
you can change this by creating a .NET host or creating a new
application domain, but it's not an ideal situation.
The bottom line is this: it is far easier to work the way that .NET
works rather than to fight against it. Read through my Fusion tutorial
for more details on assembly loading.
Fusion Tutorial: http://www.grimes.demon.co.uk/workshops/fusionWS.htm