Posts

Same problem here. I am developing my Xamarin.Forms app on my Mac (Xamarin Studio) and everything is working fine.
I just set up my new Windows 10 machine and cloned my forms project.
After opening the project in Visual Studio 2015, I am getting the exact same error as you.

Hello, I have the same issue even when deploying a new blank app (Xamarin.Forms portable class).
I can build/deploy on Windows platforms, and on the Android emulator, but not on my Android device.

When I build, I get the same conflict errors and warnings. Here is my understanding up to now. If someone can help please…

1st issue

I first get this error. Indeed, whin I check the properties of the reference "System" in the Droid project, the version reads "2.5.0.0". I can right-click on "References"-> "add reference" to open the reference manager, where I browse to only find the System 2.5.0.0 version. However, when I double-click the reference, the Object Browser opens and I can see both System 2.5.0.0 and 4.0.0.0 versions. But I don’t know how to add the 4.0.0.0 to the project…

2nd issue

VS suggests to edit the app.config file with a long list of bindings like that: I tried but it does not work.

C:\Program Files (x86)\MSBuild\Xamarin\Android\Xamarin.Android.Common.targets(2113,3): warning MSB3247: 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: <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"><dependentAssembly><assemblyIdentity name="System.Runtime" culture="neutral" publicKeyToken="b03f5f7f11d50a3a" /><bindingRedirect oldVersion="0.0.0.0-4.1.0.0" newVersion="4.1.0.0" /></dependentAssembly>

Would someone be able to upload a project that reproduces this message (Unable to resolve conflict...)? Please also include your version information. If you would prefer, feel free to PM me on the forums.

I have found an alternate solution that does not require downgrading XVS.

Using the bug report from JohnMiller dated 7 October and the bugzilla bug he mentions, this leads to the fix that was implemented for an earlier bug that apparently was solved by a couple of tweaks to the build scripts for android only.
Refer to the changes described by this commit:https://github.com/xamarin/xamarin-android/pull/273/files

I modified my msbuild target files as described and all the System conflicts went away.

@DarshanJS If you look at part of the error message it says: Choosing "System.Xml, Version=4.0.0.0 so it looks like it picks the most recent version anyway. The only reason I was even trying to resolve the issue was I was trying to troubleshoot something else and thought this might be the cause. Well, it wasn't the cause in the end anway. I don't think this is really much of an error that any of us should be worried about to be honest.