Is it possible to hold two same .NET DLLs in one app domain?

Question

0.00/5 (No votes)

See more:

Problem:
There is a process that had loaded a .NET DLL(say foo.dll) when the process start up. In another folder(say FooFolder), I got an exactly same foo.dll (same name, same version and same public token). I know if I use Assembly.LoadFrom() to load the FoolFolder/foo.dll, the FoolFolder/foo.dll will not be loaded by loader and there is only one foo.dll in the current domain.
However if I use Assembly.LoadFile() to load FoolFolder/foo.dll, the DLL was loaded successfully, but when I try to execute the code in FoolFolder/foo.dll, I will get exception of could not load "log4net.dll". (foo.dll reference the log4net.dll).

Question:
Is there any approach to load exactly same DLL in one app domain successfully? or it is impossible in .NET platform?

Posted 27-Aug-14 22:03pm

E.Diao

Add a Solution

Comments

Rob Philpott 28-Aug-14 4:41am

Have to ask - why? [Edit] I believe not, but being so weird I've never tried.

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Mayank Vashishtha · Answer 1 · 2014-08-27T22:50:00

Solution 1

I believe you don't need to do any such thing. The problem you are facing is that your code is unable to locate log4net.dll. Either the implementation is not correct or else the said dll (log4net.dll) is unavilable in the folder.

Posted 27-Aug-14 22:50pm

Mayank Vashishtha

Comments

E.Diao 28-Aug-14 21:28pm

Thanks Mayank. First, log4net.dll is available in the folder. I do not know the underlying difference between Assembly.LoadFrom and Assembly.LoadFile. MSDN does not give too much comments.

**Zoltán Zörgő** · Answer 2 · 2014-08-27T23:33:00

1) Why do you have foo.dll in two instances?
2) You can embed another assambly in the executable, is you want. See: ILMerge[^]
3) Consult MSDN[^], and see how .net locates assamblies. Eslecially this one: http://msdn.microsoft.com/en-us/library/15hyw9x3(v=vs.110).aspx[^]. Please note, that there is a log and a log viewer you can use to track resolution (see: http://msdn.microsoft.com/en-us/library/e74a18c4(v=vs.110).aspx[^]9.