title: Using Activation Context API with many dlls in different locations
body: <p>I am using Activation Context API in a .Net client running in a location A to load a COM component reg-free in location B (which is completely different location to A, not a sibling/descendent etc. on the same machine) on WS2008 by passing in location B in the ACTCTX and it works fine.</p>
  
  <p>However, I now need to do the same thing with another COM dll which in turn has dependencies on a couple of .Net COM assemblies which live in completely different locations. </p>
  
  <p>I have added the dependent .Net assemblies to the manifest and put the manifest and COM dll in location B but I have to put the dependent .Net assemblies in location A (where the client runs) to get it to work. In reality, they will live in completely different directories to location A and location B.</p>
  
  <p>Is what I'm attempting to do possible, i.e. is it possible to load multiple COM components in different unrelated directories using activation context api?</p>