Follow us on X (Twitter)  Like us on Facebook  Connect with us on LinkedIn  Subscribe to our YouTube Channel  Subscribe to our WhatsApp Group

📢 Visual Studio 2019 v16.11 to improve Git Tooling

Microsoft releases Visual Studio 2019 version 16.11, that adds few improvements to the Git Tooling and 22 bug fixes. Here's the full changelog. - Story published by Kunal Chowdhury on .

Last month Microsoft released Visual Studio 2019 version 16.10 and started releasing preview builds for Visual Studio 2019 version 16.11. The last stable release of Visual Studio 2019 was more focused on Git productivity improvements and it looks like the company is still focused on further improvements of Git integration.


Recently, Microsoft released Visual Studio 2019 version 16.11; and in this build, we could see further improvements to Git Tooling. For a detailed list of improvements added in this build, continue reading further.


Visual Studio 2019 v16.11 to improve Git Tooling


While the Visual Studio 2019 version 16.11 Preview 1 adds .NET Hot Reload User Experience for editing managed code at runtime, Visual Studio 2019 version 16.11 Preview 2 adds the following Git Tooling improvements:


  • Access additional actions from the overflow menu in the branch picker in the Git Changes window and status bar.
  • Hover over a branch name to see the last commit details in a tooltip.
  • Access additional actions in the repository picker overflow menu from the status bar.
  • Hover over a repository name to see repository details such as local path and remote URL.


Microsoft to release Visual Studio 2022 Preview 1 this year. It will be the first 64-bit version of Visual Studio which will improve the speed and performance afforded by more memory access. It will also bring new UI enhancements, more personalization options, and a continued focus on empowering developers.


Apart from these new improvements, Visual Studio 2019 version 16.11 Preview 2 also includes the following 22 bug fixes:

  • Fixed formating when providing no container name in a code search.
  • Fixed missing warning messages in CppCoreCheck.
  • Fixed a bug when adding a class in ASP.NET causing a yellow bar with the error message: 'CSharpSyncNamespaceCodeRefactoringProvider'.
  • Improved performance around using PointerSafetyXtension in CppCoreCheck.
  • Improved localization around VC++ features.
  • Fixed a build error when the solutionPath variable evaluates to undefined.
  • Fixed a rare scenario that could keep Visual Studio instances from closing if the Test Explorer is open in the solution.
  • Fixed a visibility issue with high contrast black in virtual machines shifting focus.
  • Fixed an issue where an error "No such image" occurs when removing multi-selected images that have been tagged.
  • Improved the XAML typing experience on the LiveShare client.
  • Fixed an issue when using the Navigate To with a speech recognition command causing the user to wait for the ToolTip to clear before seeing the result.
  • Fixed an issue causing previously opened documents to not restore when a solution is reopened.
  • Fixed a UWP crash when using the new Sample Data feature.
  • Fixed a bug where there were no project properties providers for "Persistence = AssemblyReference".
  • Decreased processor consumption of setup.exe.
  • Fixed an issue preventing HRESULT resources from being customized for XBOX.
  • Fixed an unhandled exception after clicking "Debug Tests".
  • Fixed a build error message "NETSDK1 031" when using a Windows Application Packaging Project.
  • Fixed a crash after ending some LiveShare Sessions.
  • Fixed a bug causing a failure of the "X" button on a page of the First Launch Wizard.
  • Fixed an "Operation not supported" error message in LiveShare.
  • Fixes a bug in Cloud Service (extended support) publish with different settings value in different service configurations.


Have a question? Or, a comment? Let's Discuss it below...


Thank you for visiting our website!

We value your engagement and would love to hear your thoughts. Don't forget to leave a comment below to share your feedback, opinions, or questions.

We believe in fostering an interactive and inclusive community, and your comments play a crucial role in creating that environment.