Bug 33826 - Broken handling of EmbeddedResource with DependentUpon in project files
Summary: Broken handling of EmbeddedResource with DependentUpon in project files
Status: NEW
Alias: None
Product: Tools
Classification: Mono
Component: msbuild ()
Version: 4.0.0
Hardware: All All
: --- normal
Target Milestone: ---
Assignee: Ankit Jain
URL:
Depends on:
Blocks:
 
Reported: 2015-09-09 12:00 UTC by Anonymous
Modified: 2017-08-28 22:48 UTC (History)
3 users (show)

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


Attachments
Test case (4.20 KB, application/x-zip-compressed)
2015-09-09 12:02 UTC, Anonymous
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 for Bug 33826 on GitHub or Developer Community if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: GitHub Markdown or Developer Community HTML
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:
Status:
NEW

Description Anonymous 2015-09-09 12:00:35 UTC
When two or more <EmbeddedResource> elements in a project file share the same parent specified using <DependentUpon> element the generated assembly contains resources with incorrect content. All the resources are generated in the resulting assembly, but all of them share contents of just one of the source files.

Attached is a test case that shows the problem.
Comment 1 Anonymous 2015-09-09 12:02:03 UTC
Created attachment 12838 [details]
Test case