Closed NightOwl888 closed 1 year ago
FYI - There is a helpful VS2022 extension upgrade guide here.
Thank you very much.
On Sat, Nov 12, 2022 at 4:57 AM Shad Storhaug @.***> wrote:
FYI - There is a helpful VS2022 extension upgrade guide here https://learn.microsoft.com/en-us/visualstudio/extensibility/migration/update-visual-studio-extension?view=vs-2022 .
— Reply to this email directly, view it on GitHub https://github.com/yysun/git-tools/pull/41#issuecomment-1312442762, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABJUM7S7KXO3YPNL3LLMZDWH5SXZANCNFSM6AAAAAAR5V46NQ . You are receiving this because you modified the open/close state.Message ID: @.***>
You're welcome.
I just realized I forgot to add the metadata to target other editions of Visual Studio 2022. It only included support for Visual Studio 2022 Community Edition.
I have added other editions in the published version.
On Sat, Nov 12, 2022 at 10:09 AM Shad Storhaug @.***> wrote:
You're welcome.
I just realized I forgot to add the metadata to target other editions of Visual Studio 2022. It only included support for Visual Studio 2022 Community Edition.
— Reply to this email directly, view it on GitHub https://github.com/yysun/git-tools/pull/41#issuecomment-1312502249, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABJUMZOGANZ5OTX3T43GC3WH6XJNANCNFSM6AAAAAAR5V46NQ . You are receiving this because you modified the open/close state.Message ID: @.***>
Fixes #40.
This is built off of the https://github.com/yysun/git-tools/tree/VS2022 branch and also targets that branch.
I ended up rebuilding the whole project piece by piece from a working menu command demo, so I don't know all of the contributing factors that were causing it not to appear. But this PR:
WindowsBase.dll
from GitApiUseCodeBase
totrue
- the menu disappeared when it wasfalse
System.ComponentModel.Composition
to the NuGet package instead of GACMicrosoft.VisualStudio.MefComponent
(which only seems to have fixed the colorization of the Git Diff window)Performance is still an issue, but I tested a release build and it doesn't seem to be any worse than the VS2019 version. I suspect there are many performance issues that could be resolved by changing it to use LibGit2Sharp instead of
System.Diagnostics.Process
to run the git commands, usingawait
, and not performing scans so frequently (or at least an option to disable it and use the refresh button manually).On a large project, the scans interfere with the
Commit
button and it sometimes takes 10-15 clicks on it before it will take. The scans also interfere with trying to rewrite commit history.At least this gets us off of VS2019, which has been out of support since April, 2022. Please roll a release ASAP.