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.
When updating MonoTouch the referenced assemblies are replaced with newer one that can be different, e.g. some types might have moved from one assembly to another .
If the solution is not rebuilt (i.e. if the reference changes are not detected) then it's likely that the linker will fail, giving hard to diagnose errors back to the user.
This may become even more important if we want to allow, in the future, switching from several MonoTouch installations (e.g. switching from 4.2 to 5.0 should duplicate the issue in ).
Lluis, is it possible for a project to detect when its referenced assemblies have changed and therefore rebuild correctly the next time the solution is compiled?
Looks like a bug in DotNetProject.CheckNeedsBuild. It checks write times on referenced projects but not referenced dlls.
This seems like the fix needs to be in DotNetProject.GetReferencedItems() so that Project.CheckNeedsBuild() would do all the work for us.
Fixed in git master.