Hello,
So we have a problem where we are trying to load DLLs from a virtual directory in the IIS. Our instance is setup so we have a clean release package as our webroot, no extra DLLs in the /bin folder, instead we have a directory outside our webroot (but on the same machine) containing those custom DLLs (custom checkout handlers and such) and a virtual directory named Customizations pointing to that outside directory in the IIS.
In our web.config in the webroot we have a simple assemblyBinding to the virtual directory:
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<probing privatePath="Customizations" />
</assemblyBinding>
but it turns out that this only works for physical directories under your webroot (which is what we are trying to avoid).
My question is, can you, load DLLs, from a directory outside the webroot in the IIS? Or am I forced to change our build process so that the DLLs under Customizations are moved into the /bin in the webroot during the deployment process?
Best regards,
Arnór
