Bug 2281 - Auto completion suggests DBNull by default
Summary: Auto completion suggests DBNull by default
Status: RESOLVED DUPLICATE of bug 1228
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: 2.8 beta 3
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2011-11-30 18:01 UTC by Andrew Young
Modified: 2011-12-05 06:07 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

screenshot example (42.82 KB, image/png)
2011-11-30 18:01 UTC, Andrew Young

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 Andrew Young 2011-11-30 18:01:30 UTC
Created attachment 978 [details]
screenshot example

Typing "o = null" will cause auto completion to default the top selection to DBNull. This can get a little annoying when you specifically want "null" because hitting either tab or enter after that will cause the editor to insert "DBNull" when you wanted "null".

See screenshot.
Comment 1 Jeffrey Stedfast 2011-11-30 18:21:52 UTC
I see this quite often as well.
Comment 2 Mikayla Hutchinson [MSFT] 2011-11-30 18:37:27 UTC
The problem is that null is missing from the completion list, which appears to be due to parser races.
Comment 3 Alan McGovern 2011-12-05 06:07:50 UTC

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