I have some problems with DotNetProjectResolver and assembly resolving.
Imagine I have a strong signed assembly A. My application is referencing a local copy of A. Then I want to dotNetProjectResolver.AddExternalReference(B) where B is referencing its own local copy of A.
I get an exception saying that same assembly can't be loaded from two different places (A and B have different paths to the same assembly). The same situation is perfectly handled by fusion (it just reuses the already loaded assembly).
Is this a bug?
Miha Markic Righthand .net consulting and software development