LSP: Insertion of new LSP powered extension into VS and/or SDK

[0101]

Need to figure out how to automatically insert the new extension into VS and/or SDK.

[T-Gro]

Idea: Have the lsp server .exe part of the SDK, nor part of VS.

[smoothdeveloper]

@T-Gro would it have an impact when bugs are fixed in the VS editor, in terms of shipping the update without requiring to install a new SDK?

I assume VS updates come at faster pace, independently from SDK, in many circumstances.

Also, what use cases would consume the LSP on it's own as an executable rather than leveraging it in a library?

if we consider ionide would be the first consumer, would they not use the library?

[T-Gro]

This is hypothetically possible, but practically very rare for F# fixes - more often then not, critical hotfixes either go to SDK only (codegen impacting) or to both (most bugs are in the typechecking area, which powers both compilation as well as editor features).