Joey Robichaud

Looks like a fix has gone into Roslyn (https://github.com/dotnet/roslyn/pull/61675). This should be resolved after we take a new build of O#.

@garym247 Can you please share the OmniSharp Log from the VS Code Output pane? As well as, the output from running `dotnet --info` from a terminal.

No the C# textmate grammar is still quite a bit behind. We would recommend enabling Semantic Highlighting.

@tn-5 Could you open an issue against https://github.com/dotnet/csharp-tmLanguage?

Focusing on a different ToolWindow or Editor then back to the Interactive Window corrects the commands being sent.

My current hunch on the issue seems to be that the CommandUIGuid on the WindowFrame is set to the Interactive Window's guid, but doesn't take effect until there is a...

Here is the script I ran prior to migrating the code into RIT - https://gist.github.com/JoeRobich/5b02dbe9b9d60b4699df546036040888

Moving this to Roslyn as .editorconfig support is implemented by the compiler.

The [Microsoft.TestPlatform.ObjectModel](https://www.nuget.org/packages/Microsoft.TestPlatform.ObjectModel/) used by the .NET Test SDK brings in an older version of NuGet than what is used by the .NET SDK. Roslyn misattributes this reference to the Microsoft.CodeAnalysis.Analyzer.Testing...

> I ran the tests again after building, and the failure showed up one more time. @carlossanlop I should have noted that the version number in my example above is...