Bug 11422 - Unable to reach breakpoints in other solutions
Summary: Unable to reach breakpoints in other solutions
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Debugger ()
Version: 4.0.3
Hardware: All All
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2013-03-26 11:35 UTC by Chris Miller
Modified: 2016-10-18 13:53 UTC (History)
4 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 Chris Miller 2013-03-26 11:35:49 UTC
I want to debug into Monotouch code compiled as a library in another solution. I can load both solutions in and set breakpoints in the library, but those breakpoints are never reached.  If I enable "Debug project code only" for the debugger under preferences, the break points are reached.
Comment 1 Jeffrey Stedfast 2013-04-08 11:53:24 UTC
I can't seem to replicate this problem. I created 2 separate solutions, one with a library project and one with an application project. I then added the library assembly to the application project's References and added a breakpoint in each of the 2 solutions. No matter what my debugger settings are, both breakpoints are hit.

Here's a screencast: http://screencast.com/t/TxjP2v91Q11
Comment 2 Regis 2013-05-01 12:01:51 UTC
I have the same problem.

I have added a class library (framework 4.0) to the solution and referenced it from the Android Application Project. (I ignored the "can't reference project because incorrect framework" message).
The code compiles and run but it is not possible to add breakpoints in the class library code, or to step into it.
Comment 3 PJ 2013-11-19 17:05:01 UTC
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?

If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
Comment 4 Regis 2013-11-20 02:55:11 UTC
@Jeffrey - create a standard .net lib, not a xamarin/android lib and try to hit a breakpoint
Comment 5 Jeffrey Stedfast 2013-11-20 07:09:25 UTC
I'll try to test this out soon
Comment 6 David Karlaš 2016-05-24 04:58:09 UTC
Sorry for so late response...
If you still have this problem... Can you check if .mdb file of library is copied with it into bin/Debug folder of your app project? I believe there was issue in past where .mdb was not copied for library in some cases, hence debugging didn't work...
Comment 7 iain 2016-10-18 13:53:54 UTC
We have not received the requested information. If you are still experiencing this issue please provide all the requested information and re-open the bug report. Thanks