Bug 2606 - No code completion for named arguments
Summary: No code completion for named arguments
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: C# Binding ()
Version: 2.9.x
Hardware: Macintosh Mac OS
: Normal normal
Target Milestone: ---
Assignee: Mike Krüger
Depends on:
Reported: 2011-12-22 00:41 UTC by Andy Selvig
Modified: 2012-01-05 08:25 UTC (History)
1 user (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 Andy Selvig 2011-12-22 00:41:32 UTC
I've noticed that argument names are not being shown in the completion list when typing in method arguments. 

This wouldn't be a huge deal except that, if you have a member of your class with the same name (case-insensitive), the completion engine overwrites the argument name you've typed with the member.

I looked through all the completion bugs and I'm pretty sure this one isn't listed yet, but I apologize if it's a duplicate. Here's some simple code to reproduce:

class MyClass {
    string Bar { get; set; }
    void MethodOne(string foo="", string bar="") {

    void MethodTwo() {
        MethodOne(bar: // <-- bar will be replaced with Bar when the colon is typed
Comment 1 Mike Krüger 2012-01-05 08:25:58 UTC
fixed in newresolver branch.