13

I need to place DLLs for my application inside subfolder. It is possible to set this subfolder via app.config:

  <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <probing privatePath="Libs"/>
    </assemblyBinding>
  </runtime>

But for some reasons I don't want to use .config file in this case. Is it possible to set probing path directly from application code? I am sure that DLLs always be within this folder.

Any ideas?

Gunther Piez
  • 29,760
  • 6
  • 71
  • 103
Victor Haydin
  • 3,518
  • 2
  • 26
  • 41

2 Answers2

14

The probing path is defined by the AppDomainSetup for the primary app domain. In the default CLR host, that AD gets automatically created before your code starts running. The only way to configure its setup is to use a .config file, it must have the same name as the exe. After which it is frozen, any changes you make in your code won't have an effect.

Workarounds are to create your own AD so you can change its setup or implementing the AppDomain.AssemblyResolve event. Neither of which compares favorably to the simple solutions: a .config file or just keeping the assembly in the right directory. Ymmv.

Hans Passant
  • 922,412
  • 146
  • 1,693
  • 2,536
5

You could just subscribe to AppDomain.CurrentDomain.AssemblyResolve and check your specific location in your handler...

Fergus Bown
  • 1,666
  • 9
  • 16
  • It seems to be slightly overcomplicated solution. I don't need to resolve assemblies manually, its enough to use standard .Net probing for my subfolder. – Victor Haydin Mar 07 '11 at 14:05
  • 2
    You can call AppDomain.CurrentDomain.AppendPrivatePath("libs") and that will work, but the method is deprecated so probably not a good idea. To use the none deprecated equivalent appears to require making a new AppDomain, which I guess you won't want to do... – Fergus Bown Mar 07 '11 at 15:06