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.
If a project references a .net assembly directly, MonoDevelop should be able to load the corresponding .mdb or .pdb file from the assemblies original location even if that assembly is set to Local Copy.
Currently if a user compiles an assembly, then references it from another project, only the .dll would be copied locally thus making it impossible to debug into that assembly when executing the application which uses it.
It definitely used to do this, and there's code to do it. Do you have a test case?
It came from a discussion on #mono this morning. A person had built monomac locally and referenced the dll and the mdb file was not copied into his applications bin/debug. Unfortunately he was on mibbit and so cannot be contacted futher.
I think this is going to be NEEDINFO forever without a test case or another report, maybe we should close it.
It does seem to work for me. I'll close this.