Bug 9455 - Layout cannot be loaded Windows 8
Summary: Layout cannot be loaded Windows 8
Alias: None
Product: Android
Classification: Xamarin
Component: Designer ()
Version: 4.2.x
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Lluis Sanchez
Depends on:
Reported: 2013-01-10 10:43 UTC by Allie Miller
Modified: 2013-12-05 18:36 UTC (History)
2 users (show)

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

0x1110009 Message (3.11 MB, image/bmp)
2013-01-23 11:31 UTC, Davide

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 Allie Miller 2013-01-10 10:43:48 UTC
Windows 8 
Visual Studio 2010
Mono for Android 4.4.54

On Windows 7, the axml loads fine.

But on Windows 8, when loading, the following message appears:
The layout could not be loaded: Could not find bool resource matching value 0x1110009
(resolved name: config_ui_enableFadinMarquee) in current configuration.
Comment 1 Davide 2013-01-23 11:31:49 UTC
Created attachment 3271 [details]
0x1110009 Message
Comment 2 Davide 2013-01-23 11:32:51 UTC
The same for Win 7 64 bit,
both on VS 2010 and MonoDevelop 3.06
Comment 3 Lluis Sanchez 2013-03-12 13:40:20 UTC
Can I get the axml?
Comment 4 PJ 2013-11-19 17:05:50 UTC
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?

If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
Comment 5 PJ 2013-12-05 18:36:18 UTC
This bug has not been changed from the NEEDINFO state since my previous comment, marking as RESOLVED NORESPONSE.

Please feel free to REOPEN this bug at any time if you are still experiencing the issue. Please add the requested information and set the bug back to the NEW (or CONFIRMED) state.