Closed wxk0248 closed 5 years ago
Working on it
I tried it myself. I changed your main Package to an AsyncPackage, the version number ranges and some other small things like Initialize to InitializeAsync. After these changes I was able to compile the project and to install it in VS2019. It just looked fine, but I can't find it in the menu, really strange. Do you have the same issues aswell?
I have not got that far yet. The codebase has stuffs support Visual Studio back to 2008. I started creating a VS 2019 extension project and migrate the package to AsyncPackage. If you want, you can create pull request. I will merge and take a look.
On Thu, Apr 11, 2019 at 5:25 PM Bernd Baumanns notifications@github.com wrote:
I tried it myself. I changed your main Package to an AsyncPackage, the version number ranges and some other small things like Initialize to InitializeAsync. After these changes I was able to compile the project and to install it in VS2019. It just looked fine, but I can't find it in the menu, really strange. Do you have the same issues aswell?
— You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/yysun/git-tools/issues/25#issuecomment-482327061, or mute the thread https://github.com/notifications/unsubscribe-auth/AAKaM341uR3Qi-TLgNGeQrJ1AS-MEdijks5vf6gtgaJpZM4chVGA .
Glad to see this is being worked on. I dropped back down to VS2017 because I rely on the Git Changes window so much when getting ready to commit. Thanks for working on this!
Made the first build to the marketplace. Continue to research and fix the issues that the diff view is not highlighting.
The latest version only supports vs2017