-
Notifications
You must be signed in to change notification settings - Fork 314
Closed
Labels
development-issueIssues encountered while developing RD, not in RD itselfIssues encountered while developing RD, not in RD itself
Description
#5121 discusses the possibility of splitting Rubberduck into a client/server architecture, to solve various performance and scaling constraints, and proposes Language Server Protocol as a possible means of implementation.
Before we invest any further in this idea, we need a proof-of-concept to explore the technology, determine whether it is suitable for our use, and identify any shortcomings.
Initially, the following approach will be attempted:
- Console-based language server operating over stdio
- LSP protocol middleware from OmniSharp source (MIT) Server NuGet, Client NuGet
- Standalone client based on AvalonEdit sample source (MIT)
Metadata
Metadata
Assignees
Labels
development-issueIssues encountered while developing RD, not in RD itselfIssues encountered while developing RD, not in RD itself