Bug 2060 - No code completion offered for constructors
Summary: No code completion offered for constructors
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: C# Binding ()
Version: 2.8 Alpha 2
Hardware: PC Mac OS
: High normal
Target Milestone: master
Assignee: Mike Krüger
Depends on:
Reported: 2011-11-16 14:15 UTC by Alan McGovern
Modified: 2015-08-20 03:24 UTC (History)
2 users (show)

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:

Description Alan McGovern 2011-11-16 14:15:20 UTC
In the monodevelop solution if i type:

var f = new FilePath ($

we get no completion.
Comment 1 Alan McGovern 2011-11-16 14:16:45 UTC
To be explicit, it should offer 'string' if i start typing 'new'. i.e.

var f = new FilePath (new $

This should offer 'string' in this scenarion, and in the more generally it should offer me T and subclasses of T which can be instantiated.
Comment 2 Alan McGovern 2011-11-16 14:19:11 UTC
Sorry, i'm mixing up two bugs here. The bug here is simply that there is no completion offered on any available constructor overloads.
Comment 3 Mike Krüger 2011-12-06 09:37:29 UTC
Comment 4 Saurabh 2011-12-29 07:08:20 UTC
Please provide more information so that we can verify this issue.