Bug 10926 - Can't debug anymore my android project with the new xamarin studio 4.0.1 nor with monodevelop 3.1.1
Summary: Can't debug anymore my android project with the new xamarin studio 4.0.1 nor ...
Status: RESOLVED DUPLICATE of bug 9433
Alias: None
Product: Android
Classification: Xamarin
Component: Debugger ()
Version: 4.6.x
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2013-03-05 18:52 UTC by jacques le thuaut
Modified: 2013-03-07 07:39 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 jacques le thuaut 2013-03-05 18:52:14 UTC
I just updated MonoDevelop for android as requested by the updater...

And I can't put breakpoints inside my code anymore... they are always disabled even at the beginning of the program.

This is critical for my project
Comment 1 jacques le thuaut 2013-03-06 02:20:00 UTC
I found a workaround : 

When I check "Fast deployment" it is OK, I can debug... 

So I can go on

Nevertheless, this is not the way I mean developing my project due to  some artefacts
Comment 2 dean.ellis 2013-03-07 07:39:15 UTC
This is a duplicate of an existing bug.

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