Missing quick fixes before members

[miloush]

I finally managed to find a simple repro I believe:

1. Create a new WPF application project.
2. Go to MainWindow.xaml.cs.
3. Type WebClient in front of MainWindow's constructor, like this:

public partial class MainWindow : Window
{
    WebClient|
    public MainWindow()
    {
        InitializeComponent();
    }
}

At this point, a quick fix for CS0246 should be offered to resolve WebClient (i.e. add using System.Net). Actual results: no quick fix (probably because CS0246 is not generated at all).

I am not sure what triggers the issue, the same thing in console application works and under certain circumstances in WPF projects too. Anyway, I believe the add using option was available at this point in previous versions.

[Pilchie]

Thanks for the report. It looks like this worked in VS2015 RTM, then was regressed in Update 1, but is now working again in internal builds. @CyrusNajmabadi Can you verify that we have good test coverage here?

[CyrusNajmabadi]

This is failing because of: #7536

We need to fix the issue that we don't get errors for incomplete members so that this works.

[Pilchie]

I could have sworn I saw this work with the latest bits...

[DustinCampbell]

This is a regression that we shipped in Update 1. I get that we'd like a compiler fix for it with #7536, but that's been pushed to 2.0. Is there a fix we can make now to fix the regressed behavior and then drive for the right fix later?

[CyrusNajmabadi]

ping @gafter This is the same issue. We don't report semantic errors on incomplete members.

[CyrusNajmabadi]

Assigning to gafter as this involved binding incomplete members.

[CyrusNajmabadi]

This is working for me: