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's not exactly a bug but more of a convenience question.
The point is that Visual Studio saves solution files as is, leaving items order untouched. MonoDevelop, however, sorts it by guid. So in the mixed environment it becomes a bit clumsy. We have a rather big solution file (about 250 projects) which gets changed quite often and merging in this case is very difficult.
Is this behaviour a somewhat deliberate or just an implementation detail? And is it possible to mimic VS behaviour?
It's an implementation detail.
VS does not actually save them as-is. Under certain circumstances VS will completely rewrite a sln file and change the order of various projects as compared to what MD writes. Having them both agree on a consistent order is quite tricky.
I haven't seen this ever since the project model rewrite. Marking as fixed.