title: Load Dependent DLL using reflection
body: <p>In my c# application , i am using reflection to load "A.dll" and use its methods to display a collection of records.</p>
  
  <p>In the code i loads the dll from another folder(d:\loader\A.dll) at runtime. </p>
  
  <pre><code>Assembly dataAssembly = null;
  dataAssembly = Assembly.LoadFrom("d:\loader\A.dll");
  </code></pre>
  
  <p>But I miss some column data in the datagridview and found that putting B.dll that was present in same folder where in A.dll was present to my exe execution path resolves the issue. However A.dll doesn't directly refer to B.dll and neither does B.dll show in reference assembiles of dataAssembly.</p>
  
  <pre><code>            dataAssembly.GetReferencedAssemblies()
              .Select(assemblyName =&gt; assemblyName.FullName);
  </code></pre>
  
  <p>Now i have a solution that B.dll is required in the exe execution path to show data but somehow i am restricted from adding it there in production environment.</p>
  
  <p>I don't know what's there inside B.dll but i am 100% sure that i need to load this while accessing A.dll in my application. </p>
  
  <p>Since i am using reflection for loading A.dll , i want to understand how i can handle this situation so that my application is able to find B.dll when it is running A.dll methods.</p>
  
  <p>The folder path for B.dll is the same as that of A.dll .</p>
  
  <p>Sorry and excuse me for the lack of understanding , but if you have any clues or hints , kindly advise.</p>