Modules accessing different versions of same DLL filename.

Topics: Prism v4 - WPF 4
Feb 4, 2013 at 2:07 AM
Edited Feb 4, 2013 at 2:11 AM
Hi, I'm using Microsoft Prism.
I'm using the .NET 4.5 build, however I think this is irrelevant to my problem.

Module1 uses a file called MyDll.dll which has a version number of 1.
Module2 uses a file called MyDll.dll which has a version number of 2.

These modules can be built and tested individually with no problems.

However, when I want to use these two modules in a single Prism application, how can I have the filename MyDll.dll in the final executing folder, when I need them both at the same time?

Feb 4, 2013 at 6:20 PM
Edited Feb 4, 2013 at 6:21 PM

As far as I know, the scenario of loading different version of an specific assemblies in your modules is currently not supported by Prism, as when loading those modules, different versions of the assembly will be also be loaded which may result in a version conflict error. In my opinion, as mentioned in this related thread, usually it's expected that all the modules consumed by the application are compatible between each other and the shell application itself, and that the versions of the assemblies they share are the same.


Agustin Adami