…pWorkspace2

….com/internal/_git/dotnet-roslyn into features/lsp_tools_host

…pWorkspace2

…roslyn

…pWorkspace2

…roslyn

….com/internal/_git/dotnet-roslyn into features/lsp_tools_host

…pWorkspace2

…ace api

Fixes https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1691478

This allows the workpsace in vscode to have changes push-through to the in-memory workspace, avoiding the need to fork the solution so often.  Implements the work done in dotnet#67443.

Implement simple debug configuration provider.

Client side change - https://devdiv.visualstudio.com/DevDiv/_git/vscode-csharp-next/pullrequest/461233

Gets us publishing an npm package that will be added as a component to VS Dev kit.

Left to do:

* [ ] Import the new service in LSP
* [ ] Make changes to VS Dev kit repo to add component
* [ ] Add integration tests in VS Dev kit

Properly hook up file open/close handling

There are two responsbilities of this type, currently:

1. Actually creating the workspace and associated types.
2. Loading a solution, running design time builds, and populating the
   stuff created in 1.

This splits those responsbilities into two types. The latter is kept
in the same name, the former is renamed to the very pithy
"LanguageServerWorkspaceFactory".

This can also be cancelled if we were to cancel the work in the queue.

If you need to open a solution, now send the solution/open LSP
notification.

…ation instead

Commit at a time will break this down a bit.

…roslyn

Disabling until we have a plan to remove the existing snippets.

Tracking here: https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1782057

Lack of ruleset service should not crash the language server

…least one Razor file

Hook up fault telemetry initialize if it's available. This now fully works as long as the right binaries are manually added to the extension folder

* [X] Tested with and without binaries being available
* [X] Tested that nupkg is produced with right dependencies
* [ ] Add as an ILogger implementation to report telemetry
* [ ] NPM package is produced

…roslyn

This sets it so the VSCode fault reporter also signs up to report telemetry that is sent through Logger.Log

…v/dawengie/InitializeRazor

…age.json

Fix compliance warnings by moving npmrc next to package.json

…el logging

Fixes https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1786584

… out there is at least one Razor file

Call into Razor when there is a razor file so Razor can produce the project.razor.vscode.json file to make things work.

Not merging until Razor bits are in and packages available. Razor PR is dotnet/razor#8559

Part of https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1782085

Update Razor ExternalAccess.Roslyn version (contains Dustin's change dotnet/razor#8586)

Fixes: https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1799870

Add a LSP command to handle complex completion edit

Address https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1777136

Corresponding PR in vscode extension:
https://devdiv.visualstudio.com/DefaultCollection/DevDiv/_git/vscode-csharp-next/pullrequest/464748

TODO:
Add test in LanguageServer.Tests

This delegates file watching to the LSP client via the LSP file watching
protocol, if it's supported. This allows us to avoid having to deal with
all the platform-specific challenges of file watching if we can.

This allows us to deal with a circularity in initialization of LSP,
where we don't know if we can use LSP yet to watch for files until
we've already tried to watch for files.

There is a DataMember attribute that has a "correct" spelling, but
the LSP spec itself has a misspelling that we must match.

This delegates file watching to the LSP client via the LSP file watching protocol, if it's supported. This allows us to avoid having to deal with all the platform-specific challenges of file watching if we can.

Roslyn assumes that the scheme portion of a URI is 'file:', however this is not the scheme for razor csharp files and the correct scheme is needed when looking up what razor documents are being tracked by Roslyn. This is a temporary workaround that checks to see if the passed in file path is one of razor's csharp files and adds the correct scheme before creating the URI.

- loading additional assemblies into IntelliCode Starred Suggestions ALC
  - assemblies are packaged with the starred suggestions npm package