Bug 7163 - Resource ID code generated in MD don't match up those from VS2010
Summary: Resource ID code generated in MD don't match up those from VS2010
Alias: None
Product: Android
Classification: Xamarin
Component: MSBuild ()
Version: 4.2.x
Hardware: Macintosh Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2012-09-13 18:34 UTC by Paul Johnson
Modified: 2012-09-18 06:10 UTC (History)
2 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 Paul Johnson 2012-09-13 18:34:08 UTC
I have editted a number of templates under MD on my Mac, committed to svn and then downloaded to my PC the next time. The Mac uses MD with the 4.2.5 plugin and the PC uses VS2010 with the 4.2.5 plugin.

When I come to commit from the PC to svn, there is a conflict in the resources file. When I examine the conflict, it appears that MD is out by 1 when generating it's resource ID codes for anything that has been changed.
Comment 1 Paul Johnson 2012-09-14 05:21:03 UTC
I'm using MD, but I've seen this problem in earlier versions. Going from VS -> MD is seemless
Comment 2 Atsushi Eno 2012-09-18 06:10:30 UTC
I'm not sure what you are expecting, but since we use Android SDK's standard way to generate resource IDs that can be used by android apps and we cannot control aapt to behave constantly between Mac and Windows, it is not fixable.