Bug 11767 - Resources defined in external library are added to Resource.designer with errors
Summary: Resources defined in external library are added to Resource.designer with errors
Status: RESOLVED FIXED
Alias: None
Product: Android
Classification: Xamarin
Component: MSBuild ()
Version: 4.8.x
Hardware: PC Mac OS
: Normal normal
Target Milestone: ---
Assignee: Atsushi Eno
URL:
Depends on:
Blocks:
 
Reported: 2013-04-12 16:04 UTC by Bryan Moulton
Modified: 2013-07-08 03:40 UTC (History)
3 users (show)

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


Attachments
Test Solution (23.12 KB, application/zip)
2013-04-12 16:04 UTC, Bryan Moulton
Details


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:
Status:
RESOLVED FIXED

Description Bryan Moulton 2013-04-12 16:04:45 UTC
Created attachment 3810 [details]
Test Solution

In reference to case #31570

When an Android project references a library project with resources defined, entries are added to the app project's Resources.designer.cs file with invalid entries. This makes the project un-buildable. See attached file.
Comment 1 Atsushi Eno 2013-05-22 14:11:17 UTC
Guess you can rename resources to lower_case.
Comment 2 Atsushi Eno 2013-07-08 03:40:27 UTC
I cannot reproduce this issue with master anymore (while I could in the past), so we most likely fixed the cause of the problem.