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
GitHub or Developer Community 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.
I have a project with project only debugging enabled and monodevelop still tries to step into the actual mono source code when I keep using 'Step Into' in this code block:
PListScheme Load (string value)
using (var reader = XmlReader.Create (new StringReader (value)))
return PListScheme.Load (reader);
I would expect to only need three "Step Into" commands to completely execute this code block. The first 'Step Into' would move me from the using statement to the return statement, the second 'Step Into' would move me inside PListScheme.Load (my code) and when that returns, the next 'Step Into' would exit the method (or in this case probably toggle back to the using statement to indicate the reader is being disposed before the method ends).
any chance you can attach your project?
This is part of some unit tests I'm developing for monodevelop from within MonoDevelop. They should be in master in a day or three, when I land all the changes.
This seems like a runtime issue assuming that setting StepRequest's AssemblyFilter property to our list of user assemblies is supposed to make it skip over non-user assemblies.
I can't repro this anymore