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.
Steps to reproduce:
1. Open some solution X with projects Foo and Bar (Foo depends on Bar).
2. Build solution.
3. Create new project Baz.
Solution X is saved to include the new project Baz.
If I hit "Build" on Foo, should not try to build Bar again.
Foo and Bar are saved, so their timestamps changes.
a) As their timestamps changes, if you build Foo, it tries to build Bar first because MonoDevelop thinks it has changed. This may be the culprit of bug 142, or maybe not.
b) If Foo and/or Bar contain some elements that MonoDevelop doesn't serialize very well, one will face the symptoms of (minor) bug 449 without need: noise in the diff when going to commit.
I'll create a pull request now that fixes this.
- When I said bug 142, I meant bug 1428.
- When I said bug 449, I meant bug 4490.
Already fixed. Projects are not saved anymore if they don't have changes.