Bug 11250 - Resource generation is missing some resource.
Summary: Resource generation is missing some resource.
Status: RESOLVED NORESPONSE
Alias: None
Product: Android
Classification: Xamarin
Component: General ()
Version: 4.6.x
Hardware: Other Other
: Normal normal
Target Milestone: ---
Assignee: Atsushi Eno
URL:
Depends on:
Blocks:
 
Reported: 2013-03-19 04:37 UTC by cheansiong
Modified: 2013-12-11 08:08 UTC (History)
3 users (show)

Tags:
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:
Status:
RESOLVED NORESPONSE

Description cheansiong 2013-03-19 04:37:11 UTC
Description of Problem:
I had a few library projects and UI projects referencing each other. 
Lets say UI (UI project) and L (Library project).

UI1 refer to UI2 and UI3.
UI2 refer to UI3.

In MonoDevelop version 3.0.6, the resources in project UI3 will be generated in all UI1, UI2 and UI3 Resource class.
In MonoDevelop version 3.1.2, the auto-generated Resource class in UI2 or UI1 does not contain the resources in UI3.


How often does this happen? 
- Always.

Additional Information:
- None.
Comment 1 Mikayla Hutchinson [MSFT] 2013-03-19 10:55:37 UTC
What do you mean, the "Resource class"? Is this an Android project?
Comment 2 cheansiong 2013-03-19 11:08:25 UTC
I'm sorry for less information. Yes, it is android project. I should say UI1 and UI2 doesn't contains all the resources from UI3.
Comment 3 cheansiong 2013-03-20 21:57:17 UTC
Hi there, Is there any updates on this issue?
Comment 4 Atsushi Eno 2013-06-21 05:15:18 UTC
Sorry for late reply. I don't understand the scope of this problem.
If there is Resource.designer.cs for each project and there is missing IDE support that lacks autocompletion, then it is rather an IDE issue.
If there are corresponding Resource.designer.cs but there are only partial resource set, then it is likely Xamarin.Android issue.
If there isn't Resource.designer.cs in some library, make sure that your library project was created only after certain version of Xamarin.Android or Mono for Android (I believe it was 4.4.xx of some large number). Your library csproj files need to have <AndroidResgenFile> and <AndroidResgenClass> properties, as well as those files to exist.
In any sense, we have working libraries with android resources, so it is not reproducible only in that broad description. Please provide a reproducible solution if that problem still occurs. Thanks.
Comment 5 PJ 2013-11-19 17:04:27 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 6 PJ 2013-12-05 18:34:30 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.
Comment 7 cheansiong 2013-12-07 00:59:45 UTC
Sorry, I think I missed your replied email and eventually raised another bugs (Bug 16429)

In the latest comment in Bug tracking no. 16429, it is much closer to the problem that I had.
Comment 8 Atsushi Eno 2013-12-11 08:08:53 UTC
There is no reason to keep this bug open. Closing again.