..NET isn't designed to work that way. If you want to put a dll outside of
the application's bin directory, then you'll have to put it in the GAC or
another place the clr commonly looks for assemblies. Alteratively, you can
load the class dynamically using the System.Reflection namespace, but the
nightmare results aren't worth the hassle. Why not store your class
libaries in the GAC if they are being used by more than one app? That's
what the GAC is for.
I was minding my own business when wpy blurted out:
I wrote aspnet application with code behind then compile it to dll. The
web application will use class library dll that I wrote. After compilation,
the library dll and interface dll will put together into bin. Now I want to
put my class library dll into other folder together with other class library
dlls. But error occur if I move the class library dll to other location.
How can I separate interface dll and class library dll.
--
Insert corny line here