Closed NGumby closed 2 years ago
Thanks for the PR. Unfortunately, your approach will result in the extension no longer working in previous versions of Visual Studio . Fo full support, this extension must be split in two.
Would it work to merge this PR then publish the extension to the VS marketplace with a different identifier? The 2017 compatible version could remain (though, be difficult to maintain) and a 2022 version would be newly available. (I don't know much about how marketplace.visualstudio.com works)
Create a branch of the old one for patching and then merge the new one into master and deploy it as a new extension to the marketplace?
Fixes #99 Based on the work of https://github.com/chenxustu1/FileNesting
Much appreciated
@madskristensen hey Mads, in one of my extensions, https://marketplace.visualstudio.com/items?itemName=AlexanderGayko.VarAdorner , i managed to get one extension working in VS2017, 2019 and 2022 (basically by reflection-dynamic 'ing around the platform specific parts of the VS packages) - wouldn't that be a better approach for the time being?
Fixes #99 Based on the work of https://github.com/chenxustu1/FileNesting