Quick Links

The root assembly conflicts with another assembly

Answers

@Thomas.Bienkowski said:
As mentioned by Homero, a workaround was posted. This is already fixed for the next version,

Eh... No so much.

11jun2017

I hadn't updated my home system in months. VS2017 was still Release Candidate - So that had to update.
The Mac also was just as far behind.
After countless rounds of updating on the Mac - it is up-to-date as of version v.yesterday. Same with the PC.
As we all know if you don't have exactly matching versions you can't even connect to the mac build host. So the fact that I can, it doesn't drop off, it wants to build, it makes files and so on, makes me think everything is up-to-date and hunky-dory on both sides.

I just fixed by updating Visual Studio 2017 (PC) to latest version using update feature in the VS 2017 installer. Updated OSX El Capitan to MAC OS Sierra, updated XCode to latest version 8.3.4 and updated Xamarin Studio Mac to latest version also. Now working without build error.

It was definitely related to version compatibility between dev env and MAC emulator env. Versions must be compatible for it to work.

I encountered the same issue while trying to build the iOS version of the app in VS2015.
After spending almost a day finding what the problem could be and what is the solution to it, this just worked like a charm.
Thanks to @Thomas.Bienkowski.
Cheers!

@TertiumOrganum said:
Guys, do you ever launch (stable!) release on your PCs/Macs before go online? Every single update of Xamarin in VS and then on Mac is a huge headache! Your update tools never work (thanx they give links for manual download), and when I update every single time I spend day or two to make it work. And many people have the same pain. Why does it happen?

In my two years of being a xamarin developer, I've never experienced a smooth upgrade.

Each update is 'superficial' - that is - they only update xamarin to keep up with the latest version of Xcode; very few critical bugs are fixed each release. And each release is progressively worst than the last. I honestly do not believe they have a QA (Quality Assurance) team. If they do, then they need to do a much better job of regression testing.

Microsoft takes a major LOSS for the acquisition of this company. If I were Bill Gates - I would have forced the company to produce a "good" product before I gave them a single dollar...Xamarin is far from being a "good" product, heck it barely works most of the time.

If you want a stable iOS development experience - it'd be best to just learn Xcode at this point. Xamarin just can't get their stuff together.

For anyone else having trouble locating this file to modify, here's where I found it on my PC (Win10 w/VS2017):
C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.After.targets

For me it was simply the case of renaming my build output for my common project, as otherwise the Mac project conflicted with the Common project with the same name, even though their suffixes are different.

Double click on your common project (or right-click, options on Mac)

Go to the Output Tab

Change your assembly name to include the suffix Common, i.e. MyProject becomes MyProjectCommon