Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
Tested with: XA 5.1.5, VS2013, VS2015, XS
1. Create Android Class Library project
3. Look in output directory
See .mdb file for class library.
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.
This used to work, I think in earlier cycle 5 builds, but I don't know for sure.
This does appear to be a regression in C5SR2, perhaps related to/fallout from our old friend #30318.
Looks to be an intended behavioral change after all, there's likely no action required for changing behavior here.
Discussion on slack  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?
This is just fall out from the pdb->mdb changes in #30318. Its totally expected :)