Question

We have a Silverlight 5 project and we currently have a folder of shared library DLL’s. We are in the process of changing to use NuGet for these libraries wherever possible.

One of the NuGet packages we want to use is MVVMLight, to replace the MVVM Light SL4 DLL’s we are currently using, which were never upgraded when we moved from SL4 to SL5.

However, when we installed the NuGet package containing the SL5 DLL’s it automatically changed our existing references to the Microsoft.Practices.ServiceLocation DLL file to one which came with the MVVM Light package, which has the same version number, but a different public key.

This has caused a conflict with some of our other code which is using the Prism library, which uses the Microsoft.Practices.ServiceLocation DLL, but, signed with the original public key.

Obviously we cannot use the same named DLL twice in the same folder, so, any suggestion on how to resolve this issue, whilst keeping both Prism and MVVM Light packages installed from NuGet.

Thanks very much,

Martyn.

Answer 1

I have exactly the same problem with Microsoft.Practices.ServiceLocation.dll. In my case, this could be resolve if the nuget package of MvvmLight was dependent of CommonServiceLocator as I suggested here : http://mvvmlight.codeplex.com/discussions/429311

So far, no news about that.

Edit : Laurent just push a version of MVVM Light using the CommonServiceLocator from Nuget.