Hi Harold,
Based on my understanding, what Agustin means is that you cannot use you own version ofMicrosoft.Practices.Prism.dll along side the original Prism assemblies, asPrism uses strong named assemblies, thus generating the exception you are mentioning. Hence, if you wish to use your custom version ofPrism, you will need to rebuilt and replace ALL the Prism assemblies.
For doing so, when building your custom Prism solution, you will need to copyALL of the following assemblies to the environment where your application is running:
- Microsoft.Practices.Prism.dll
- Microsoft.Practices.Prism.Interactivity.dll
- Microsoft.Practices.Prism.UnityExtensions.dll (only required if you are usingUnity)
- Microsoft.Practices.Prism.MefExtensions.dll (only required if you are usingMEF)
(As far as I know, you still should be able to use the original Microsoft.Practices.ServiceLocation.dll andMicrosoft.Practices.Unity.dll assemblies without problems.)
Also, take into account that you will need to change all the references to the aforementioned assemblies in the application to point your custom versions, by manually removing and adding the references.
Regards,
Damian Cherubini
http://blogs.southworks.net/dcherubini