Matteo Prosperi

@vsrs could you elaborate on what issues you noticed with the VS implementation of the LSP protocol? VS implementation of LSP is (or at the very least is supposed to...

Hi Everybody, Visual Studio 2022 RC released today has an LSP implementation that is compatible with rust-analyzer. I tested it and you can see some screenshots at the end of...

@clemenswasser, what I did was only a test integration. I basically followed the [guide here](https://docs.microsoft.com/en-us/visualstudio/extensibility/adding-an-lsp-extension?view=vs-2022). I packaged `rust-analyzer.exe` within my VSIX, so the meaningful part of my code would only...

> @matteo-prosperi is it possible that you could share your extension? I tried making my own, but can't get it working 😢 Also would it be okay for you, if...

I cannot think of an option that would work fully with a mix of local and remote targets and overlapping IDs. Do you think it would be a good improvement...

> What do you mean IProgress already works that way? `$/enumerator/next` is handled by `JsonRpc.rpcTargetInfo.TryGetTargetMethod` which results in the message being dropped if the token is unrecognized. `$/progress"` is handled...

I would not add a second attribute: it seems too verbose to me. I don't have a good reason for rejecting this, except that I like the current clean separation...

I think having a property in the attribute is a good idea. On Wed, Jul 26, 2023, 22:29 Andrew Arnott ***@***.***> wrote: > I suppose rather than a new attribute...

Thanks for the update. This is great news for modules that need to support a large range of PS versions!