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.
The IDE hangs up and then the project is not loadable anymore. After deleting the .userprefs file the project can be loaded successfully again.
The .userprefs file looks like a common XML file without declaration. So why not check the file against a XSD Schema? The IDE would the be able to catch the error early.
Can you attach the userprefs file that causes the hang?
It really wouldn't help to use an xsd schema. That would catch malformed data, but not bugs in *handling* of the data. Anyway, the format is extensible, so it's not possible.
After playing around awhile I found out that it is NOT a userpefs fault. It seems that the IDE is hanging up on launching the Layout Designer. For my first steps with Mono for Android I only used the code editor to change the file main.axml. But if this file is open in code editor (and stored in userpefs) and then you quit and restart the program. The IDE wants to open this file in the Designer not in the code editor. So in the summary it is something with the designer and the ide do not remember if a .axml file was opened in code or designer.
The Layout Designer kills my IDE in anyway even if I doubleclick a .axml file in an open project. Limitation in trial version?
Workaround: delete all files with .axml out of your files-section in .userprefs
This is caused by an incompatibility with the Android SDK when you have the new API level 16 installed. A fix for MonoDevelop will be released soon.
*** Bug 6134 has been marked as a duplicate of this bug. ***