Keeping source code neatly formatted and ensuring coding styles are consistent is something I’ve never been good at. To automatically perform a git pull upon solution load, try out the free Git Pull extension. Then assign any shortcut to it and hit the OK button.
From there, find the command from the list. Go to search ( Ctrl+Q) and type “ keyboard” to find the Environment > Keyboard options page. Previously, Team Explorer’s pull command was not a command you could assign keyboard shortcuts to but now it is. What I really wanted was a keyboard shortcut from within Visual Studio that did it for me. The only way to do git pull in the past was to either use Team Explorer, the command line, or an external tool. The result is that I end up with merge conflicts and other nuisances. But, as it turns out repeatedly, this is something I tend to forget. That means I must make sure to do a git pull before I make any subsequent commits. I do a lot of work with GitHub repos and I often take pull requests from people. Uncheck both the Reopen documents on solution load and Restore Solution Explorer project hierarchy on solution load checkboxes.Īn added benefit from unchecking these two checkboxes is that solutions will load faster too, because of the eliminated overhead from restoring state. Go to search ( Ctrl+Q) and type in “ load” to find the Projects and Solutions > General options page. This feature is now native to Visual Studio 2019 and can be enabled with two separate checkboxes. I wrote the Clean Solution extension to provide this behavior in previous version of Visual Studio. That’s great but I prefer a clean slate when I open solutions – no files open and all the tree nodes collapsed in Solution Explorer. When a solution is closed, its state is saved so that next time you open it, Visual Studio can restore the collapsed/expanded state of projects and folders in Solution Explorer and reopen the documents that were left open. I want to share a few of them with you since they are not all obvious and some require you to change some settings. During this time, there has been a lot of little features that have put a smile on my face and made me more productive. But I’ve been using Visual Studio 2019 exclusively since the first internal build – long before the release of Preview 1 in December of 2018. A few days ago, we announced the general availability of Visual Studio 2019.
0 kommentar(er)
