Add missing compiler tests and dependency projects to the solution filter

[333fred]

No description provided.

[333fred]

@dotnet/razor-compiler for review. I would suggest commit-by-commit review for ease of understanding the changes.

@dotnet/razor-tooling f43572a is the one commit that you really need to review. There isn't a shared test library between compiler and tooling, so I didn't add the testing utility reference to the tooling layer, but you should feel free to add it and start taking advantage of the diff helpers if you want.

[333fred]

IRazorCapabilitiesProvider was marked obsolete.

[davidwengier]

Thanks, noticed this change merged in last night, and was going to respond today :)

[davidwengier]

Turns out this breaks running tooling tests locall, so going to have to revert. We need to wait for these roslyn bits to be in a VS build.

EDIT: To be clear, I'll just revert this specific change to the RazorCapabilitiesProvider. The rest of the PR is fine :D

[davidwengier]

Nope, even reverting this, just having the new roslyn dep breaks running unit tests for me. I don't know what to think any more.

[333fred]

Thanks everyone!

[davidwengier]

you should feel free to add it and start taking advantage of the diff helpers if you want.

We currently have an uglier way to acheive the same result:

razor/src/Razor/test/Microsoft.AspNetCore.Razor.LanguageServer.Test/CodeActions/CSharp/CSharpCodeActionEndToEndTest.cs

Line 410 in 450c0a1

new XUnitVerifier().EqualOrDiff(expected, actual);

I will try to make them nicer, but annoyingly, adding the reference to the CodeAnalysis.Testing package introduces some namespace collisions.