Bug 37301 - XamlC error on MasterDetailPage compilation
Summary: XamlC error on MasterDetailPage compilation
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 2.0.0
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Stephane Delcroix
Depends on:
Reported: 2015-12-28 11:22 UTC by Rasmus Christensen
Modified: 2017-01-18 13:24 UTC (History)
4 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 Rasmus Christensen 2015-12-28 11:22:28 UTC
I'm creating an app where I use a MasterDetailPage. I have a local namespace registered where I get the Master and Detail pages from. If I enable XamlC as compile in app.cs I get an error when setting the Detail page. If I remove the compile attribute, there is no error at either compile or runtime. 

I also have a description here https://forums.xamarin.com/discussion/58252/xamlc-on-assembly-level-breaks-on-masterdetailpage-setting-detailpage-in-xaml#latest

I don't think the XamlC compiler should break on this?

Best regards
Comment 1 Stephane Delcroix 2016-09-09 07:50:24 UTC
Could you please attach the simplest sample triggering this issue to this bug ?
Comment 2 Stephane Delcroix 2017-01-18 13:24:39 UTC
no response in a year. I guess the problem is gone