Bug 40747 - VS XamlApp: Forms Xaml View derives from ContentPage instead of ContentView
Summary: VS XamlApp: Forms Xaml View derives from ContentPage instead of ContentView
Status: RESOLVED FIXED
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Xamarin.Forms ()
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2016-04-28 00:45 UTC by adrianknight89
Modified: 2016-07-14 02:25 UTC (History)
6 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:
Status:
RESOLVED FIXED

Description adrianknight89 2016-04-28 00:45:53 UTC
Testing out the new XamlApp VS template with Cycle 8 and XF 2.3.0.34-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 :)
Comment 1 Chris King 2016-04-28 19:57:46 UTC
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?

Warm regards,
XFT
Comment 2 adrianknight89 2016-04-28 20:18:31 UTC
@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.
Comment 3 Daniel Cazzulino 2016-05-09 20:57:31 UTC
Fixed, and we also took the chance to improve a bit on the template naming.

Thanks!
Comment 4 adrianknight89 2016-07-14 02:25:38 UTC
When will this fix be released? Should we expect it in Cycle 8 stable?