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 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.
Randomly the designer totally destroys the .axml file (erasing part of the file at the end) when opening the .axml file.
This seems to happen more frequently when having edited the .axml file in the xml editor (normal visual studio xml editor) before opening the same file in the designer.
Since this requires the user roll back to an earlier commited version of the same file it makes the whole process of working with the designer too much of a pain to be worthwhile, hence I tend to not use it anymore.
It's ok to put up an error message in case the designer isn't developed enough to handle the xml, but it certainly isn't ok to just shred source files.
I've tried working with the designer in MonoDevelop and there I haven't seen any of these problems.
Are you still seeing this problem with Xamarin.Android 4.6?
I have only used MonoDevelop lately, but I worked in VisualStudio for a day now, and no I didn't see this problem anymore in VisualStudio with Xamarin.Android 4.6.
OK, closing for now.
Today, with the latest builds:
And now the issue does not exists. As the designer is working fine for VS as well as for XS.
Hence, closing this issue.