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.
As a work around until full custom support is available, the Designer could render and allow properties to be set for the closest parent view that it supports. For example, if I sub-class FrameLayout, allow me to interact with a FrameLayout in the designer.
The Android layout system is very powerful and allowing me to be much more productful than equivalent iOS development. But I am having to create a lot of "helper" classes to extend stock views instead of sub-classing since I will lose designer support. I hope that above suggestion is not too difficult and could be given priority consideration. Thanks.
"full custom support" -> "full custom view support"
This should be higher priority. It makes the designer useless once you insert any custom controls.
With full custom control support this should be fixed now.
As of the latest version (7.1) this is still not fixed, at least in VS for MacOS v7.1, widgets like Spinners or custom TextViews are showing up as grey boxes in the Designer, and when using RecyclerViews I get a ClassNotFoundException error.
Is there a fix for this?