Split extension into PreVS2022 and VS2022 projects #13
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.
Summary
This splits the extension in two; PreV2022 and VS2022. The PreVS2022 project targets VS2017 and VS2019, as before.
Both projects have been modernized to use
PackageReference
. Both projects now use the Microsoft.VisualStudio.SDK NuGet package, instead of all the separate legacy extension libraries. The only real differences between the projects are the versions they use of the NuGet packages and thevsixmanifest
.Shared code was placed in the new
LineSorter.Shared
project. Other shared files was placed in aSharedFiles
folder, and linked into each project.Notes
LineSorter.Export
project to increase maintainability for the futureMicrosoft.VisualStudio.MPF.15.0
because that is only needed pre-VS2010 (see blog post)BackgroundProjectLoad_string
ProvideAutoLoad
attribute, as it was marked as obsolete in VS2019, and the other auto load attributes should be enough