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 1382 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
*** Bug 571 has been marked as a duplicate of this bug. ***
So it turns out this is actually a complicated change. Migration is handled on a per-project basis but upgrading to vs2010 needs to be done on a per-solution basis. As such, there is no simple and clean way to detect that one of the projects has been migrated and therefore the entire solution needs to be moved to VS2010.
This would need to be planned out before being implemented. I'll defer on this one for now. While it isn't the greatest UX, it's not completely awful.
Can't you query MD to see if the project is part of a solution and then test that solution, and if 2k8, upgrade? it's a project change that kicks this off anyway, for example, if you add a folder to a project, then it tells you the solution needs to be upgraded to vs 2k10. folder info is stored in the project, not the solution.