Bug 3635 - No Type Autocompletion for object initializers
Summary: No Type Autocompletion for object initializers
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Text Editor ()
Version: 2.8.6
Hardware: PC Mac OS
: Normal normal
Target Milestone: ---
Assignee: Mike Krüger
URL:
Depends on:
Blocks:
 
Reported: 2012-02-24 11:16 UTC by Eric Beisecker
Modified: 2012-02-27 06:31 UTC (History)
1 user (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 Eric Beisecker 2012-02-24 11:16:48 UTC
Current Behavior: When using an object initializer, Autocomplete does not provide a hint as to what is a valid type to set the object property too.

Expected Behavior: Autocomplete should give hints as to what is a valid type to set an Objects property too.

Screencast: http://screencast.com/t/IQCgAiX1

Versions:

MonoDevelop 2.8.6.5
Mono 2.10.8
Comment 1 Eric Beisecker 2012-02-24 11:49:41 UTC
Related, No autocomplete is displayed at all in List Collection initializers.

Screencast: http://screencast.com/t/2nfrgnYy
Comment 2 Mike Krüger 2012-02-27 06:31:08 UTC
Fixed that context.

However a problem in variable initializer context remains - but that's handled by a different bug case.