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 on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
It looks like the Migration tool (Classic to Unified) is dependent on monotouch.dll being referenced and built.
I'm getting this error in XS logs with XI 10: https://gist.github.com/VincentDondain/b2b0e0d7dcbaa16253cfda25931c9c84
Our msbuild error when people try to build a project that uses Classic with XI 10 suggests that people run the migration tool so the priority of this bug might be fairly high.
That's a circular issue, if we can't remove it to allow migration then it stays...
Can that code be changed to load something else ? e.g. if `monotouch.dll` is not present, then try loading `monotouch-migration.dll` ?
If so we could rename the assembly (instead of deleting it) until the next cycle (where it won't exists in any form). At that point the migration message should point people to support (and get people an older version of the tools).
Also is there other assemblies being loaded like this ? e.g. MonoTouch.Dialog-1.dll ?
Team, because this breaks the functionality on the IDE, let us ship the monotouch.dll on this release, and then in the future, we can coordinate with the IDE team what to do about removing the migration tool or using a differently named assembly.
We could just ship the old binaries for now, we do not need to build them.
https://github.com/xamarin/xamarin-macios/pull/799 adds back the assembly so the migration should work again.
PR was merged and a 10.0.0.x build should come out of
I just tried that new Xamarin.iOS build (with latest XS) and I can confirm that we do get the expected build error when building a classic project. The message mentions how you're supposed to migrate and the migration works as expected.
As per comment 5, this issue is resolved for Vincent, hence closing this issue by marking it as Verified.