I have a .NET console app that references a DLL. It runs fine if the DLL is in the same folder as the EXE but I would like to put the DLL in a different folder. How can I do that?
+1
A:
If the DLL is loaded dynamically, just specify the full path to it. If it's static, or you feel like it, add the library path to the PATH environment variable. Yes, this DOS relic is still around.
Also, read the doc on the LoadLibrary() API for a better understanding of DLL loading.
Seva Alekseyev
2010-01-05 21:03:03
+3
A:
If the dll is in a sub folder you can add this folder to the AppDomain private path.
The private bin path of an AppDomain cannot be changed once the AppDomain has been created (AppDomain.AppendPrivatePath is obsolete), if you don't want to create a new AppDomain, you can modify the probing element in the App.config.
If it's not in a sub folder, things get more complicated, you can load the assembly using its full path, but if it references other assembly, the CLR won't be able to resolve the dependencies.
If you want to resolve dependencies, you can add an handler to AppDomain.AssemblyResolve and fetch the needed assembly in your specific folder.
Another possibility is to place this dll (and dependencies) in the GAC.
SelflessCoder
2010-01-05 21:07:40
But if you add the path to the process's own environment's PATH, then dependent libraries will be resolved. And there will be much rejoicing.
Seva Alekseyev
2010-01-05 21:18:33
Depending on the environment PATH makes deployment harder, if it can be avoided you can gain much rejoicing ;)
SelflessCoder
2010-01-05 21:27:17
Document the `<probing>` element in the app.config file to make your post perfect.
Hans Passant
2010-01-05 21:30:18
I'm talking about adjusting the private PATH of the process, not the systemwide PATH. I had to do it once so that a whole DLL tree of third-party libraries loads right. Otherwise, you can load one library by full path, but *its* dependencies from the same folder then fail to load.Just throwing 2-cent coins towards the OP here...
Seva Alekseyev
2010-01-05 21:30:45
@nobugz Done, thanks for the suggestion.
SelflessCoder
2010-01-05 21:44:37
It seems like I can't do any of these things because the FileNotFound is thrown before Main even starts executing!
JoelFan
2010-01-05 23:05:16
Where is the assembly you are trying to reference, is it in a sub folder of the folder containing the exe? FileNotFoundException would indicate that you reference the assembly explicitly in your project, you can't do this if the assembly isn't in a subfolder and the probing element is configured correctly.
SelflessCoder
2010-01-06 00:27:14
I added the reference in Visual Studio... it is not a subfolder of the exe. It works from Studio, but not stand-alone.
JoelFan
2010-01-06 17:11:41
As for adding a handler to AssemblyResolve... I can't seem to find an example of how to do this in a way that I can also call the default handler (or allow it to run naturally) in most cases... just handle the specific DLLs I need to.
JoelFan
2010-01-06 17:13:49
Then you can't reference the assembly explicitly without setting Copy Local to true in the reference property page. Maybe you should give more detail about your context in your question if you want an answer.
SelflessCoder
2010-01-06 17:57:30
A:
Well you could have the application look in certain directories that you can specify in a configuration section. Then you could load them up at the start of your application. I don't really know what you are trying to do, but this could be a solution.
Assembly.Load("Assembly.Name")
If you aren't building some kind of plugin architecture, I would think about why you have to do this.
Khalid Abuhakmeh
2010-01-05 21:07:43