Bug 31619 - Microsoft.Common.targets don't copy .mdb file of referenced .dll file
Summary: Microsoft.Common.targets don't copy .mdb file of referenced .dll file
Status: NEW
Alias: None
Product: Tools
Classification: Mono
Component: xbuild ()
Version: unspecified
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2015-07-03 07:03 UTC by David Karlaš
Modified: 2015-07-03 07:03 UTC (History)
1 user (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 for Bug 31619 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:

Description David Karlaš 2015-07-03 07:03:36 UTC
If you create 2 projects one library and one console app.
Build library. Then in console app reference .dll in bin/Debug of library project...
Build Console app, you will see only .dll is in Console app output folder without .mdb. This step must be added to Microsoft.Common.targets

Bug 9588 is maybe duplicate, but that one has patch and is addressing this in code... Not sure what approach is best...