Update samples to deploy in VS 2026#129
Merged
gregg-miskelly merged 7 commits intomicrosoft:mainfrom Jan 22, 2026
Merged
Conversation
Member
|
LGTM |
plnelson
approved these changes
Jan 22, 2026
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
2 participants
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.
Several of the samples in this repo were using .vcxproj files to package and deploy Visual Studio extensions. This doesn't currently work with VS 2026, so this migrates these projects to use .csproj files for deployment.
This also makes sure all the projects are using the same version of the VS SDK, and all the .sln files are marked as being from Visual Studio 2026.
This resolves #128