[WIP] VS for Windows language extension compatibility test#99
Draft
lextm wants to merge 10 commits intoMattParkerDev:mainfrom
Draft
[WIP] VS for Windows language extension compatibility test#99lextm wants to merge 10 commits intoMattParkerDev:mainfrom
lextm wants to merge 10 commits intoMattParkerDev:mainfrom
Conversation
…ation status message
This was referenced Mar 29, 2026
Author
|
Extend the .vsix import to work for simple VS Code extensions too. One example is this one for reStructuredText.
|
…dling for non-workspace files
…g and descriptions
Author
|
Svelte language support from VS for Windows can be imported with highlighting and completion.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.


This is not a pull request that aim to be thoroughly reviewed or merged, because I use Claude to produce it for just a few evaluation goals,
If this simple test case can pass, then we can move on to experiment with language server (which many more modern language extensions use), and even deeper integration with a VS for Windows compatible extensibility SDK.
Of course, it revealed many gaps (like current tight/direct integration with Roslyn, not over the standard language server protocol). That's why such experiments are important even before 1.0 is shipped.
I agree to the terms of contributing as stated here