-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Walkthrough: Create Custom Language Editor issues. #50
Comments
If anyone comes across this, I'm trying to work out how to create a "hello world" language server over at https://github.com/grokys/HelloWorldExtension and documenting my findings along the way. |
Actually, this same seems to implement what I personally would think of as a custom language editor: https://github.com/microsoft/VSSDK-Extensibility-Samples/tree/master/Ook_Language_Integration So I'm a little confused as to where It would have been nice to watch the linked video but it seems like with many things VSSDK-related, it no longer exists. |
But then I watch this video: https://www.youtube.com/watch?v=VNhmk1oR3R4 And this uses Now I'm really confused as to what I should be doing. |
Ok, thank you GitHub copilot. This is the explanation (hopefully it's correct). It still doesn't explain why I might need Choosing between IVsColorizer• Use Case: This is an older approach primarily used in earlier versions of Visual Studio or for integrating with legacy systems. It directly interfaces with Visual Studio's text editor to provide syntax coloring. ITaggerProvider• Use Case: IClassifierProvider• Use Case: RecommendationFor most scenarios involving syntax highlighting in modern Visual Studio extensions,
In summary, for new extensions focused on syntax highlighting, start with Apologies for the noise, but hopefully someone coming along later may find it useful. |
This walkthrough has a number of issues, the most important being that the linked repostiory https://github.com/SFC-Sarge/LinqLanguageEditor2022 is now dead.
In addition to this, there are several problems:
LinqLanguageEditor2022Package.cs
file should look like this now:" has theProvideEditorLogicalView
attribute at line 1429, but you're not told to add it until line 1530I'd suggest that a guide the concentrates on adding support for a simple theoretical language, and explains why each step needs to be done would be more useful.
The text was updated successfully, but these errors were encountered: