Closed orbikm closed 1 year ago
Ok, I reverted what I believe was the result of a bad merge / rebase. The PR is now in a functional state, ready for review.
Hi and thanks for the contribution. It would be great if you could rebase it onto master. I can test and merge it more easily there.
I just created #146 which is this same PR but rebased onto master. Feel free to close this Pull Request in lieu of the other.
This feature implements behavior for allowing a user to specify a custom root path for all JSON settings for each project. This works by allowing the user to specify the Root path, and the Solution name and Project names are added to the path.
This allows for saving modified Command Line arguments in a Source Control solution, while having an ephemeral Visual Studio project (such as the case when the VS projects are generated by a build system). Due to this, this resolves issue #115
A description of how we would plan to use this in practice would be something like:
NOTE: This is based upon the
vs2022
branch, as that was the only version of Visual Studio I had installed at the moment, so I could test with it. I wanted to ask the author / maintainers if they would prefer that I rebase this change on top ofmain
, I can do that. I wasn't sure if vs2022 branch was close to being merged or not (given that the extension is published to the Marketplace with a 2022 version).