Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report for Bug 41060 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
Created attachment 15988 [details]
I have VS 2015 update 2.
I created a new solution: Blank App (Xamarin.Forms Portable)
and after it finishes laying out the devices projects.
and checking the Xamarin.Forms that comes with VS 2005 u2, its: v126.96.36.19982
I Compile it with the:
Menu Tools\Options\Projects and Solutions\Build and Run\MSBuild project build output verbosity: Detailed
and without adding any nugets or references, i have conflicts between dlls, as you can search for the string "There was a conflict between" in the attached file:
Then i went to nuget for the entire solution and updated the "" for all projects to the latest stable version: v188.8.131.52
Then i compiled it, and also got conflicts in dlls, as you can see them in the attached file:
Both files are in the this link:
An actual reproduction solution would be helpful here to see what the result is on another machine. Have you tried removing all of the Forms packages, adding them again (preferably with newer versions) and cleaning/rebuilding?
Thanks, You can see the test project in this link:
and if you open the "Output-Build.zip" file, and search for "There was a conflict", you have at least two of them.
This appears to be happening because of a reference to MonoAndroid's mscorlib 184.108.40.206 in the default Android project in the "New Project" template.
Still happening as of 220.127.116.11.
I'm not sure this is actually a problem, though. In both cases, the conflict is resolved by the build system and there doesn't seem to be a problem at runtime.