![]() ![]() It's not Microsoft, but GitHub who has extended vscode and they added the support for their platform through extensions and open source contribution to the editor directly. On the other hand you have VS Code, which is used by GitHub itself internally, runs in a browser, powers v and github codespaces and doesn't carry the legacy if Visual Studio 2022. Many old extensions are no longer available in VS2022 or the authors are still working on a new version that conforms to the new requirements. Some tool vendors may invest in native integration into Visual Studio in the future. It looks like that may be changing though. But their priorities have been in advanced git scenarios for a long while, not in building support for vendor specific issue integration. It's much faster too and the new architecture allowed the team to build interactive rebase, multi-repo support, submodule support and more. The new git experience is no longer constrained by the Team Explorer window, is a top-level citizen in Visual Studio and can finally use easier to remember keyboard shortcut keys. Unfortunately this all happened at the expense of some features. Vendors may add menu items to the top level menu, but they currently can't extend the new git window.Īt the same time, Visual Studio 2022 dropped support for the built-in browser window, which was a memory hog, loads IE11 and also needed full retooling to support the 圆4 out-of-process loading that Visual Studio 2022 now demands.Īll of this work now allows Visual Studio to use more memory, it's faster and by moving extensions out-of-process, it has greatly improved the performance and stability of the visual studio platform. This window is a pure git client and it's vendor agnostic. So Team Explorer and its old undocumented extensibility points were dropped and the new Git Window was born. NET Core and 圆4 and to support out-of-process extensibility to properly support Visual Studio 2022 anyway. As such it's a breeding ground for bugs and it needed to be ported to. The concept of the Team Explorer window also wasn't ideal for hosting GitHub, Azure DevOps, BitBucket and every other tool-vendor that wanted to be listed and there was very little in the way of control for users to set the order of elements or hide certain tiles. This has caused many interesting issues in the past. Over time other vendors snuck their way into Team Explorer, but mostly through undocumented and unsupported ways. It stems from 2005 when Team Foundation Server first got released. NET 4 and was very much geared towards integrating with Azure DevOps. With the new Git experience the Visual Studio team opted for a more agnostic approach. The "old" team explorer did a number of really nice things, but it was also very hard to integrate into for other tool vendors. How might I regain that functionality with GitHub and Visual Studio 2022? As described above, this was functionality that worked with Azure Repos but is lost with GitHub integration. From that post, I am most interested in the " Working on issues" bit. I have found a VS Code blog post that enables a lot of this functionality (and more) into VS Code, but I've yet to find anything for Visual Studio 2022. And the "Create Pull Request" menu items simply launches the browser to the GitHub page there's no integration there, either. I have to now manually type in the issue number if I want to link a commit to the issue. Since I can't view the issues, I can no longer automatically create branches that are linked to the issue. ![]() The Team Explorer window no longer contains a "Work Items" view. When I connect to a GitHub repository, that integration is lost. I can easily create a branch from one, link it automatically, and submit pull requests. When connected to an Azure Repo, the VS Team Explorer window includes a "Work Items" view that shows open issues from Azure Boards. How do I view and integrate with GitHub issues using Visual Studio 2022?
0 Comments
Leave a Reply. |