Bug 54247 - Cannot reference AppCompat resources in library project without empty xml files in Resources
Summary: Cannot reference AppCompat resources in library project without empty xml fil...
Alias: None
Product: Android
Classification: Xamarin
Component: MSBuild ()
Version: 7.0 (C8)
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: dean.ellis
Depends on:
Reported: 2017-03-29 20:39 UTC by Jeremy Kolb
Modified: 2017-08-23 21:14 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 Jeremy Kolb 2017-03-29 20:39:03 UTC
If I have a library project that references Xamarin.Support.V7.AppCompat as an example I CANNOT reference any symbols from the support lib (such as Resource.Layout.support_simple_spinner_dropdown_item) UNLESS I do the following in my project:

1. Create a Resources\ folder.
2. Create a Resources\Xml folder.
3. Add Empty.xml to the folder above with the following contents:
<?xml version="1.0" encoding="utf-8" ?> 

Once I do that `Resource.Designer.cs` is generated and I can then reference `Resource.Layout.support_simple_spinner_dropdown_item` from my library's namespace.
Comment 1 Jon Douglas [MSFT] 2017-07-05 18:41:53 UTC
This seems like a undocumented limitation or issue with tooling not generating the Resource.designer.cs file without the respective folder. Can you please attach a sample reproduction with steps to reproduce this? This will help us confirm this issue and figure out a better way to make this easier to work with.

Thank you!
Comment 2 Cody Beyer (MSFT) 2017-08-23 21:14:57 UTC
Because we have not received a reply to our request for more information we are closing this issue. If you are still encountering this issue, please reopen the ticket with the requested information. Thanks!