Missing highlighting in razor editor

[MarvinKlein1508]

The razor editor does it again @davidwengier

To reproduce:

1. Clone https://github.com/microsoft/fluentui-blazor
2. Open solution in Visual Studio Insiders 11116.177
3. Open file: FluentUI.Demo.Shared->Pages->Lab->IssueTester
4. Add @code { } block
5. Type public class DemoObject { }
6. See razor editor going crazy - even after a restart

Please take a look on the attached video:
https://www.youtube.com/watch?v=2_VjzgG0xM8

[davidwengier]

Sorry to do this to you @MarvinKlein1508, but that's not the razor editor, that's our good friend copilot. Would you be able to log this through VS Report a Problem? If you chuck the link in here, I'll make sure it gets to the right team.

[MarvinKlein1508]

@davidwengier are you sure about this? The highlighting of the class keyword and of the generic type of the list should work though. But I can report it via Report a problem as well. I do everything to get a better razor editor since I'm spending like 80% of my day in it

[davidwengier]

Oh sorry, I thought you were talking about the constant flashing of the suggestions. Let me take a closer look at the video

[davidwengier]

Oh okay, YouTube compression is doing us no favours, but looks like class DemoObject is all black? Yeah, okay, thats us. Let me see if I can repro, if I can't it still might be worth a VS feedback recording, just to get some traces etc.

[davidwengier]

Okay, I can't repro, but I suspect thats because I'm using a version that has a fix for an issue that a lot of people are running into right now. In fact, this is likely a duplicate of your other issue you logged, just manifesting in different ways. If you want to go ahead and report through VS Feedback, I'll confirm with logs etc.

[MarvinKlein1508]

@davidwengier I sent a report using VS with the request to assign it to you for the logs.

[davidwengier]

Feedback report: https://devdiv.visualstudio.com/DevDiv/_workitems/edit/2616560

[davidwengier]

Thanks for the report @MarvinKlein1508, I can see in the logs an issue that should have been fixed by #12301. I am not seeing the one I expected (which would have been fixed by #12338) but either way I think after 18.3 Insiders comes out you should hopefully not hit this issue any more.

[MarvinKlein1508]

@davidwengier do you know the version number for that?

I updated today to: Insiders [11201.2]