Forum Xamarin.Forms
We are excited to announce that the Xamarin Forums are moving to the new Microsoft Q&A experience. Q&A is the home for technical questions and answers at across all products at Microsoft now including Xamarin!

We encourage you to head over to Microsoft Q&A for .NET for posting new questions and get involved today.

Should I worry about a version conflict now I've updated to latest Xamarin (

EasyGoingPatEasyGoingPat GBMember ✭✭✭
edited October 2019 in Xamarin.Forms

I've just updated to latest Visual Studio (16.3.4), latest Xamrin nuget package (, and updated a the Mono SDK on my Mac Build host to match.

I now get the following warning in the build output:

**3> No way to resolve conflict between "System.Runtime.Serialization, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089" and "System.Runtime.Serialization, Version=, Culture=neutral, PublicKeyToken=7cec85d7bea7798e". Choosing "System.Runtime.Serialization, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089" arbitrarily.
Should I worry about this? Is there any way to fix it?


Best Answer


  • ColeXColeX Member, Xamarin Team Xamurai

    Try this solutions post in this thread :

    1. The warning disappeared after adding a reference to System.Runtime.Serialization (4.0.0) to each of the projects with the warning.

    2. Try to use update-package -reinstall command in the Package Manager Console.

  • EasyGoingPatEasyGoingPat GBMember ✭✭✭


    The update-package -reinstall command didn't fix it. I tried to add a reference to System.Runtime.Serialization but it doesn't seem to be on my PC (anywhere that I can find).

    I though that ticking Auto-generate binding redirects in iOS Project Properties -> Application should fix it but that didn't work either.

    The application seems to run okay. I'm just nervous of a build that says it is arbitrarily choosing an assembly. :s

    • Patrick
  • EasyGoingPatEasyGoingPat GBMember ✭✭✭


    Sorry, I misunderstood. I thought I was looking for a reference to V4.0.0.0, not V2.0.5.0.

    That did indeed fix it (though I still don't really understand why).

    Thank you.

    ~ Patrick

Sign In or Register to comment.