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.
Testing out the new XamlApp VS template with Cycle 8 and XF 184.108.40.206-pre1. I noticed a bug which I hope could be solved soon. When you add a new Forms Xaml View, code-behind derives from ContentPage instead of ContentView.
Looking forward to using the VS previewer (when it comes out) + XamlApp :)
Are you saying that Add > New Item > Cross-Platform > Code > Forms Xaml Page produced code behind that derives from ContentPage whereas you'd like it to derive from ContentView? If so, why is that unexpected behavior?
@Chris King Not Xaml Page but Xaml View. See my original post. Xaml Page is fine, but Xaml View derives from ContentPage instead of ContentView.
Fixed, and we also took the chance to improve a bit on the template naming.
When will this fix be released? Should we expect it in Cycle 8 stable?