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.
When working on a MonoTouch app (not sure if this matters), whenever I find myself typing something along the lines of:
if (fu != null
MonoDevelop always autocompletes that null as DBNull, and I have to backspace and then type null again (usually typing it again, "null" appears in the completion list and things work ok).
You'll probably notice that the first time you type null, the value "null" does not appear in the completion list. Once you backspace over the DBNull, then start typing null again, "null" *does* appear in the completion list.
Happens for me in any project type.
*** Bug 1414 has been marked as a duplicate of this bug. ***
*** Bug 2281 has been marked as a duplicate of this bug. ***
fixed that one in newresolver branch.
We have verified this issue with MonoDevelop 2.8.5 ad MonoTouch 5.0.4,it is working fine.
Kindly close this issue.
This is still happening in the new resolver branch:
Seems that the parser has regressed in local variable declarations :/
public static void Main (string args)
string str =
I insert now always "null" till the local variables are fixed.
Opened #3468 because this breaks much more than just the "null" case.