Bug 59531 - autogenerating XAML
Summary: autogenerating XAML
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2017-09-15 19:16 UTC by Roman
Modified: 2017-09-15 19:25 UTC (History)
2 users (show)

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:

Description Roman 2017-09-15 19:16:33 UTC
When I add new page (class which is inherited ContentPage) using VisualStudio 2017 I'm forced add to XAML one string:


because without it application crashes
Comment 1 Paul DiPietro [MSFT] 2017-09-15 19:23:26 UTC
Yes, this is required for identifying your namespace in the XAML. You should likely stick to the defaults provided by the page template in most cases.
Comment 2 Paul DiPietro [MSFT] 2017-09-15 19:25:18 UTC
Please refer to these docs which discuss use of xmlns:local: