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 MonoDevelop serializes a project back to msbuild XML, it often discards or reformats parts of the document because it does not keep any knowledge of the original XML in its internal model.
Whitespace and line ending differences are a source of git/diff headaches when project files are manipulated by VS and MD, for example.
This is sort of related to bug 2612.
That's not true, we do keep an XmlDocument, and simply replace the actual items/properties that were loaded into our internal model. Everything else should be untouched. Additionally, I'm pretty sure we detect and preserve line endings. We use the same whitespace formatting that VS does.
Can you provide specific examples of removed elements, and whitespace and line ending changes?
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?
If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
This bug has not been changed from the NEEDINFO state since my previous comment, marking as RESOLVED NORESPONSE.
Please feel free to REOPEN this bug at any time if you are still experiencing the issue. Please add the requested information and set the bug back to the NEW (or CONFIRMED) state.