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.
Just found what looks like a bug in the Property List Editor.
I decided to foray into using child panes in Settings. So I created a new plist called 'Advanced' and linked to it from Root.plist.
So far so good. But when I create a PSTextFieldSpecifier entry, it refuses to allow me to add a DefaultValue key to the dictionary. It *will* allow this when I am editing Root.plist, but not in Advanced.plist.
I was able to add this XML Element using TextEdit and it sure seems to be working, although I have not tested this exhaustively yet. But what the heck is the problem with the Xamarin.Studio plist editor? Or am I missing something?
Xamarin Studio 4.0.2 should be hitting stable today or tomorrow, I think. When it goes live (or you can install it from the Beta channel if you are up for it), can you check this again?
It appears to work for me and I *do* recall fixing a DefaultValue bug after 4.0 was released.
Just got Studio 4.0.2.
The 'Default Value' problem appears to be fixed. Cool!