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.
For code like:
if (workingTreeIterator.IsModified(dirCacheIterator.GetDirCacheEntry(), true))
it can be really handy to put a breakpoint on DoStuff (). When the breakpoint is hit you then put a breakpoint in 'IsModified' and execute the contents of the 'if' statement in the immediate window. This allows you to easily break execution after something fails/succeeds which shouldn't and then step through the statement by re-executing it.
However when the statement is exceuted from the immediate window, monodevelop ignores the breakpoints.
I think this must be runtime?
This happens because md requests it by passing InvokeOptions.DisableBreakpoints to InvokeMethod ().
I'm tempted to say that this is by design... but perhaps there can be a setting for whether or not the runtime should break when evaluating a statement in the Immediate Window (you wouldn't want this behavior in the Watch window, for example)