Bug 32624 - Android class library projects do not generate .mdb files on Windows
Summary: Android class library projects do not generate .mdb files on Windows
Alias: None
Product: Android
Classification: Xamarin
Component: MSBuild ()
Version: 5.1
Hardware: PC Windows
: High normal
Target Milestone: ---
Assignee: dean.ellis
Depends on:
Reported: 2015-07-30 13:40 UTC by Sandy Armstrong [MSFT]
Modified: 2015-08-10 04:27 UTC (History)
3 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 Sandy Armstrong [MSFT] 2015-07-30 13:40:15 UTC
Tested with: XA 5.1.5, VS2013, VS2015, XS

1. Create Android Class Library project
2. Build
3. Look in output directory

Expected results:

See .mdb file for class library.

Actual results:

No .mdb file, just a .pdb file.

Workaround: create an Android app project that reference the class library, and the .mdb will be generated in the app output directory. Alternatively, use pdb2mdb.
Comment 1 Sandy Armstrong [MSFT] 2015-07-30 13:40:57 UTC
This used to work, I think in earlier cycle 5 builds, but I don't know for sure.
Comment 2 Peter Collins 2015-07-30 13:56:36 UTC
This does appear to be a regression in C5SR2, perhaps related to/fallout from our old friend #30318.
Comment 3 Peter Collins 2015-07-30 17:44:53 UTC
Looks to be an intended behavioral change after all, there's likely no action required for changing behavior here.
Comment 4 Peter Collins 2015-08-07 13:45:43 UTC
Discussion on slack [0] suggested that this was intended due to the behavior change in the fix for #30318.

@Dean was there any further investigation needed here? Should we resolve this?

[0] https://xamarinhq.slack.com/archives/android/p1438288794004947
Comment 5 dean.ellis 2015-08-10 04:27:20 UTC
This is just fall out from the pdb->mdb changes in #30318. Its totally expected :)