Completion is broken typing a property in a @code block without automatic brace completion

[davidwengier]

Originally posted by @michaelcsikos in #4336 (comment)

Here's another thing that drives me nuts. Declaring a simple auto property with literally nothing else in the razor file. It makes no difference if the [Parameter] attribute is in-line or on the line above. I type get; and on the ; keystroke VS changes it to GetHashCode; so I hit Ctrl + Z 3 times then type set; and again on the ; keystroke VS changes it to SetParamatersAsync; requiring another Ctrl + Z.

Pressing escape before typing ; closes the Intellisense menu which prevents the change to GetHashCode or SetParamatersAsync but it doesn't stop VS from moving the get; to the next line.

This is not complicated code — it's about as simple as it gets. And Visual Studio royally stuffs it up. This is the entire file:

@code
{
    [Parameter] public string ToolTip { get; set; }

}

VS needs to get out of our way. Let us turn these garbage formatting options off! I feel like VS has gotten worse with every new release since 2013, or maybe even 2010.

[davidwengier]

@333fred is this an error recovery issue? Without the closing brace on the property decl, the generated document is putting that line (line 5 in the GIF above) inside the BuildRenderTree method, so Roslyn completion is confused.

[DamianEdwards]

Seems like the code gen should always be promoting anything after @code { to the class level, irrespective of closing braces.

[michaelcsikos]

@davidwengier I now have the long-awaited 17.6.0 installed which is supposed to resolve Add option to turn off On Type formatting. I have set Options > Text Editor > Razor (ASP.NET Core) > Advanced > Format On Type to False.

Was this supposed to resolve the unwanted format on paste, too? This is by far my biggest annoyance.

[davidwengier]

@michaelcsikos sadly no, format on paste is outside of our control and happens at a higher level in the IDE. We are pushing for the right team to add an option for it however.

FYI @kayle