I'm currently in dependency hell, all I'm trying to do is leverage Azure.Storage & MobileServices from my PCL. I've been trying for five days now and there seems to be no end to the inane dependency issues these two frameworks bring, even though they're for the same service made by the same author.
I've attached the most recent debug log if anyone cares for a look.
My suspicion is that Azure.Storage uses old versions of the System namespace. I get this from the AsmSpy output. What I don't comprehend is why there's no capability to load different versions of the "same assembly" when NuGet packages are so inanely explicit about it.
I'm going to keep updating this post to keep my sanity and incase I'll solve it other might benefit.
Made a clean project and it seems Newtonsofts.Json framework is a LARGE offender, the latest version 7.0.1 apparently explicitly uses the 184.108.40.206 version of System.Runtime.Serialization and pretty much everything else.
220.127.116.11 by Newtonsoft.Json
Now excuse me I'll see if I'm able to change these dependencies or somehow make the version number implicit.
Note: Even though there's assembly conflicts the app continues to work. That's until I add MobileServices though.
I've been on stackoverflow without any woking solutinos a dozen of times now for these issues;
Failed to add reference to 'System.Data'. Please make sure that it is in the Global Assembly Cache.
could not resolve conflict between system.runtime.serialization
could not load microsoft.data.edm
I also get this warning in the Error List:
Severity Code Description Project File Line
Warning Found conflicts between different versions of the same dependent assembly. In Visual Studio, double-click this warning (or select it and press Enter) to fix the conflicts; otherwise, add the following binding redirects to the "runtime" node in the application configuration file: Gem.Droid