We have implemented a custom language that includes numerous standard features such as syntax highlighting, goto definition, IntelliSense, a debugger, and some code lens, among others.
At present, everything is based on the .NET Framework, with projects in our language consuming C# .NET framework project dependencies and vice versa.
Assuming that these changes will eventually allow us to generate .NET core assemblies.
I’m interested in understanding how the extensibility features activated in this repository and a Language Server interact. What would be the expected combination of strategies needed to implement our current setup, but with our code written in .NET 9?
For your custom language, do you have a LSP-based language server implemented? Are you asking how you can create an extension which can communicate with your language server to provide support in Visual Studio?
We have implemented a custom language that includes numerous standard features such as syntax highlighting, goto definition, IntelliSense, a debugger, and some code lens, among others.
At present, everything is based on the .NET Framework, with projects in our language consuming C# .NET framework project dependencies and vice versa.
Assuming that these changes will eventually allow us to generate .NET core assemblies.
I’m interested in understanding how the extensibility features activated in this repository and a Language Server interact. What would be the expected combination of strategies needed to implement our current setup, but with our code written in .NET 9?
I’m struggling to piece everything together.