Question

In a C# console application, I’m trying to use <probing privatePath=""/> to point to dlls that are not in my application subdirectories. I’m using:

<runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
        <probing privatePath="D:\Library\References" />
    </assemblyBinding>
</runtime>    

This does not work, because privatePath is looking for subdirectories in my application. Is there a way to use absolute paths in this way? If not, what is the best way to point to dlls that are located outside of my application? I also tried using <codebase> with a file:/// path, but still got a System.IO.FileNotFound exception.

<runtime>
  <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
    <dependentAssembly>
      <assemblyIdentity 
        name="MyLibrary" publicKeyToken="29989D7A39ACF230" />
      <codeBase
        version="2.0.0.0"
        href="http://file:///D:/Library/References/NLog.dll"/>
    </dependentAssembly>
  </assemblyBinding>
</runtime>

but still got a System.IO.FileNotFound exception.

Answer 1

according to MSDN:

You can use the element only in machine configuration or
publisher policy files that also redirect the assembly version.
…
If you are supplying a code base hint for an assembly that is not
strong-named, the hint must point to the application base or a
subdirectory of the application base directory.

You probably tried to apply in in app.config?

and

The directories specified in privatePath must be subdirectories of the
application base directory.