Bug 57575 - Embedded Forms convert-to-native extension methods namespaces
Summary: Embedded Forms convert-to-native extension methods namespaces
Status: RESOLVED ANSWERED
Alias: None
Product: Forms
Classification: Xamarin
Component: Windows ()
Version: unspecified
Hardware: PC Windows
: Low enhancement
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2017-06-17 11:47 UTC by Matthew Leibowitz
Modified: 2017-06-17 14:04 UTC (History)
2 users (show)

Tags: embedding, ios, android, uwp
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 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.

Related Links:
Status:
RESOLVED ANSWERED

Description Matthew Leibowitz 2017-06-17 11:47:32 UTC
On Android, the namespace for the `CreateFragment` extension is `Xamarin.Forms.Platform.Android`. 

On UWP, the equivalent namespace is `Xamarin.Forms`. Not only is the inconsistency something :), but that particular namespace adds several conflicting types: Page, Grid, Button, etc.

The same goes for iOS, it uses the large `Xamarin.Forms` namespace.

To avoid conflicts, I would suggest using the `Xamarin.Forms.Platform.<platform>` namespace. Not only is this extension method very platform specific, but we won't accidentally start using Forms types in the native app.
Comment 1 David Ortinau [MSFT] 2017-06-17 14:04:50 UTC
Thanks Matthew, this is noted in our 3.0 backlog to look at.