There seem to be a few NuGet version conflicts causing the tests for fail, but for some reason I can't get the errors to repro locally on my machine. :( Will take a closer look tomorrow.

There seem to be a few NuGet version conflicts causing the tests for fail, but for some reason I can't get the errors to repro locally on my machine. :( Will take a closer look tomorrow.

dotnet nuget locals all -c should get your box into a similar state

/azp run

@dotnet/razor-tooling This should now be ready to review whenever anyone has some time. Everything appears to be working, with two caveats:

1. Having an .editorconfig may still mess up override completion in Razor files (i.e. you'll still observe the original issue). This can occur if the .editorconfig C# tabs/spaces options differ from the Tools->Options C# tabs/spaces options. I believe this is due to the .editorconfig options provider taking precedence over the Razor options provider. I'm thinking we may want to completely disable the .editorconfig options provider for Razor files until we have proper support for .editorconfig. I think this can be done in a follow-up PR on the Roslyn side.
2. As previously discussed offline, I'm seeing VS hang whenever trying to commit an override completion item for the first time. Taylor mentioned he wasn't able to repro this, so I'm hoping it's just a "me" problem. Filed a feedback ticket with a dump here: https://developercommunity.visualstudio.com/t/razor-ide-hangs-when-trying-to-commit-override-com/1453744