Bug 10678 - When "Fast deployment" is unchecked, the debbuger never breaks on breakpoints
Summary: When "Fast deployment" is unchecked, the debbuger never breaks on breakpoints
Status: RESOLVED DUPLICATE of bug 9433
Alias: None
Product: Android
Classification: Xamarin
Component: Debugger ()
Version: 4.8.x
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2013-02-26 04:41 UTC by softlion
Modified: 2013-05-18 16:56 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 softlion 2013-02-26 04:41:38 UTC
create an android project with Xamarin Studio or Visual Studio.

In the project properties, uncheck "Fast Deployment".

Add a breakpoint to the first line of the OnCreate method.

Run the app with debugging enabled.

=> the debbuger never breaks on the breakpoint.
=> if you use "pause" to force a break, all modules are grayed and displayed as "external" modules.
Comment 1 Jeremy Kolb 2013-03-05 14:13:44 UTC
I'm seeing this on 4.6 as well and it's really hurting me.
Comment 2 dean.ellis 2013-03-06 13:49:42 UTC
This is a duplicate of Bug 9433.

*** This bug has been marked as a duplicate of bug 9433 ***