Completion bug writing 'Task.'

[mkrueger]

It's a bug from the monodevelop bug tracker but affects VS.NET as well.

See: http://screencast.com/t/Xebulsw8

Seems to be always in that case:

Task.$ await Task

[DustinCampbell]

This is a tricky parser issue. The problem is that the parser is parsing as a local declaration there the variable name is Task and the type is Task.await. Passing to the compiler team to see if there's something better we can do here.

[Suchiman]

I'm not sure if that's the same problem but here's a very similiar case:

using System.Threading.Tasks;

namespace IntelliSenseRepro
{
    public class SharingController
    {
        private Test Service => new Test();

        public async Task Test()
        {
            $
            await Service.SaveChangesAsync();
        }
    }

    public class Test
    {
        public async Task SaveChangesAsync() { }
    }
}

Go to $ and type Service.. Everything in the method is red underlined then 😉 and no IntelliSense 😦

If you change the Code to:

using System.Threading.Tasks;

namespace IntelliSenseRepro
{
    public class SharingController
    {
        public async Task Test()
        {
            Test Service = new Test();
            $
            await Service.SaveChangesAsync();
        }
    }

    public class Test
    {
        public async Task SaveChangesAsync() { }
    }
}

then everything after $ is still red squigglied but at least IntelliSense pops up and gives correct completion.

[jaredpar]

@gafter recovery work appears to have fixed this too. No longer repros on VS 2017.