Bug 1228 - typing null autocompletes to DBNull most of the time
Summary: typing null autocompletes to DBNull most of the time
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Text Editor ()
Version: Trunk
Hardware: PC Mac OS
: High normal
Target Milestone: master
Assignee: Mike Krüger
URL:
: 1414 2281 ()
Depends on:
Blocks:
 
Reported: 2011-10-04 10:35 UTC by Jeffrey Stedfast
Modified: 2015-08-20 03:24 UTC (History)
8 users (show)

Tags:
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:
Status:
RESOLVED FIXED

Description Jeffrey Stedfast 2011-10-04 10:35:57 UTC
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.
Comment 1 Alex Rønne Petersen 2011-10-04 11:54:18 UTC
Happens for me in any project type.
Comment 2 Mike Krüger 2011-10-11 10:13:10 UTC
*** Bug 1414 has been marked as a duplicate of this bug. ***
Comment 3 Alan McGovern 2011-12-05 06:07:50 UTC
*** Bug 2281 has been marked as a duplicate of this bug. ***
Comment 4 Mike Krüger 2011-12-12 12:28:24 UTC
fixed that one in newresolver branch.
Comment 5 Saurabh 2011-12-29 04:44:57 UTC
We have verified this issue with MonoDevelop 2.8.5 ad MonoTouch 5.0.4,it is working fine.

Kindly close this issue.
Comment 6 Lluis Sanchez 2012-02-14 04:47:44 UTC
This is still happening in the new resolver branch:

http://screencast.com/t/pYHAWzzVT
Comment 7 Mike Krüger 2012-02-15 03:16:18 UTC
Seems that the parser has regressed in local variable declarations :/

------------
class C
{
	public static void Main (string[] args)
	{
		string str = 
	}
}
------------

I insert now always "null" till the local variables are fixed.
Comment 8 Mike Krüger 2012-02-15 03:19:43 UTC
Opened #3468 because this breaks much more than just the "null" case.