This is Xamarin's bug tracking system. For product support, please use the support links listed in your Xamarin Account.
Bug 53021 - [XF/XVS] ObservableCollection incorrectly named in Forms MasterDetail Page Xaml template
Summary: [XF/XVS] ObservableCollection incorrectly named in Forms MasterDetail Page Xa...
Status: RESOLVED FIXED
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Templates (show other bugs)
Version: 4.3.0 (C9)
Hardware: PC Windows
: --- normal
Target Milestone: 15.2
Assignee: Pierce Boggan [MSFT]
URL:
Depends on:
Blocks:
 
Reported: 2017-03-03 15:52 UTC by Al Clark [MSFT]
Modified: 2017-04-14 10:14 UTC (History)
8 users (show)

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


Attachments
Image with Error Warning after adding Form MasterDetails (79.09 KB, image/png)
2017-04-14 10:14 UTC, Swati Gangrade
Details

Description Al Clark [MSFT] 2017-03-03 15:52:29 UTC
=== Overview ===

ObservableCollection is incorrectly named in Forms MasterDetail Page Xaml tamplate.

=== Steps to Reproduce ===

1. Create a new blank Xamarin Forms PCL project.
2. Right-click PCL and Add > Forms MasterDetail Page Xaml

=== Expected Behaviour ===

New MasterDetail Page should be loaded error-free.

=== Actual Behaviour ===

ObservableCollection MenuItems is later referred to as [NameOfPage]MenuItems (where [NameOfPage] is the name of the MasterDetail page).
Comment 1 Al Clark [MSFT] 2017-03-03 15:53:01 UTC
Linked to same template as this bug:
https://bugzilla.xamarin.com/show_bug.cgi?id=53020
Comment 3 Swati Gangrade 2017-04-14 10:14:23 UTC
Created attachment 21539 [details]
Image with Error Warning after adding Form MasterDetails

@Alan Clark and @Pierce Boggan

 verify this bug I used steps provided in screencast attached with this bug.

I have observed that after adding Forms MasterDetail Page.Xaml there is 2 warning. I have attached screenshot, that illustrates the warning message received. 

Can you please clarify the actual and expected result more specifically.

Note You need to log in before you can comment on or make changes to this bug.