{"id":224896,"date":"2019-04-04T08:00:25","date_gmt":"2019-04-04T15:00:25","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/visualstudio\/?p=224896"},"modified":"2019-04-04T08:28:05","modified_gmt":"2019-04-04T15:28:05","slug":"little-great-things-about-visual-studio-2019","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/visualstudio\/little-great-things-about-visual-studio-2019\/","title":{"rendered":"Little great things about Visual Studio 2019"},"content":{"rendered":"

A few days ago, we announced<\/a> the general availability of Visual Studio 2019<\/a>. But I\u2019ve been using Visual Studio 2019 exclusively since the first internal build \u2013 long before the release of Preview 1 in December of 2018. During this time, there has been a lot of little features that have put a smile on my face and made me more productive.<\/p>\n

I want to share a few of them with you since they are not all obvious and some require you to change some settings. Let\u2019s dive in.<\/p>\n

Clean solution load<\/h2>\n

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. That\u2019s great but I prefer a clean slate when I open solutions \u2013 no files open and all the tree nodes collapsed in Solution Explorer.<\/p>\n

I wrote the Clean Solution<\/a> extension to provide this behavior in previous version of Visual Studio. This feature is now native to Visual Studio 2019 and can be enabled with two separate checkboxes. Go to search (Ctrl+Q<\/em>) and type in \u201cload<\/em>\u201d to find the Projects and Solutions > General<\/em> options page.<\/p>\n

Uncheck both the Reopen documents on solution load<\/em> and Restore Solution Explorer project hierarchy on solution load<\/em> checkboxes.<\/p>\n

\"\"<\/h2>\n

An added benefit from unchecking these two checkboxes is that solutions will load faster too, because of the eliminated overhead from restoring state. Win-win.<\/p>\n

Git pull from shortcut<\/h2>\n

I do a lot of work with GitHub repos and I often take pull requests from people. That means I must make sure to do a git pull<\/em> before I make any subsequent commits. But, as it turns out repeatedly, this is something I tend to forget. The result is that I end up with merge conflicts and other nuisances.<\/p>\n

The only way to do git pull<\/em> in the past was to either use Team Explorer, the command line, or an external tool. What I really wanted was a keyboard shortcut from within Visual Studio that did it for me.<\/p>\n

Previously, Team Explorer\u2019s pull command was not a command you could assign keyboard shortcuts to but now it is. Go to search (Ctrl+Q<\/em>) and type \u201ckeyboard<\/strong>\u201d to find the Environment > Keyboard<\/em> options page. From there, find the Team.Git.Pull<\/em> command from the list. Then assign any shortcut to it and hit the OK button. I chose to use Ctrl+Shift+P<\/em>.<\/p>\n

\"\"<\/p>\n

To automatically perform a git pull<\/em> upon solution load, try out the free Git Pull<\/a> extension.<\/p>\n

Code Cleanup for C#<\/h2>\n

Keeping source code neatly formatted and ensuring coding styles are consistent is something I\u2019ve never been good at. The new Code Cleanup feature is a huge help in keeping my code neat and tidy since I have configured it to run all the fixers by default.<\/p>\n

To do that, go to the Code Cleanup menu sitting in the bottom margin of the editor window and click Configure Code Cleanup<\/em>.<\/p>\n

\"\"<\/p>\n

In the dialog, select all the fixers one by one from the bottom pane and hit the up-arrow button to move them up into the top. Then hit OK.<\/p>\n

\"\"<\/p>\n

Now all fixers will run every time you perform a Code Cleanup. Simply hit Ctrl+K, Ctrl+E<\/em> to execute. The result is a nicely formatted document with a bunch of coding style rules applied, such as added missing braces and modifiers. Voila!<\/p>\n

IntelliCode<\/h2>\n

IntelliCode is a new feature that augments the IntelliSense completions based on the context you\u2019re in using advanced machine learning algorithms. That proves useful for many scenarios including when you are exploring new interfaces or APIs. I write a lot of Visual Studio extensions and the API surface is so big that there are parts of it I have never used. When I\u2019m exploring a new part of the Visual Studio API, I find it very helpful to have IntelliCode guide me through how to use it.<\/p>\n

\"\"<\/p>\n

To enable this powerful feature, you can download IntelliCode<\/a> from the Visual Studio Marketplace and install the extension.<\/p>\n

IntelliCode works for C#, C++ and XAML.<\/p>\n

See content of Clipboard Ring<\/h2>\n

Every time you copy (Ctrl+C<\/em>) something in Visual Studio, it is being stored in the Clipboard Ring. Hitting Ctrl+Shift+V<\/em> allows you to cycle through the items in the Clipboard ring and paste the item you select. I find it very useful to keep multiple things in the clipboard at once and then paste the various items to specific locations.<\/p>\n

In Visual Studio 2019, the Clipboard Ring now shows a visual preview of its content when hitting Ctrl+Shift+V<\/em>. That makes it easier than ever to navigate through the copy history and select the right item to paste.<\/p>\n

\"\"<\/p>\n

New C# Refactorings<\/h2>\n

There are lots of new and highly useful refactorings in C# that I\u2019ve come to depend on every single day. They show up as suggestions in the light bulb and include moving members to interface or base class, adjusting namespaces to match folder structure, convert foreach-loops to Linq queries, and a lot more.<\/p>\n

\"\"<\/p>\n

To learn more about the new refactorings and other C# features in Visual Studio 2019, check out this post on the .NET blog<\/a>.<\/p>\n

Git Stash<\/h2>\n

Having the ability to stash away some work for future use is super helpful. Git Stash is what gives me that ability without having to create a new branch. If you\u2019re familiar with TFS, you can think of Git Stash as a shelveset.<\/p>\n

\"\"<\/p>\n

The best part is that I can manage all my stashes inside the Team Explorer window. They are easy to create and apply, and I\u2019ve been using them a lot more after Visual Studio now natively supports them.<\/p>\n

Try Visual Studio 2019<\/h2>\n

These were just a few of the many small improvements found throughout Visual Studio 2019 that I find particularly useful. Please share any tips or improvements you\u2019ve found helpful in the comments below!<\/p>\n","protected":false},"excerpt":{"rendered":"

A few days ago, we announced the general availability of Visual Studio 2019. But I\u2019ve been using Visual Studio 2019 exclusively since the first internal build \u2013 long before the release of Preview 1 in December of 2018. During this time, there has been a lot of little features that have put a smile on my face and made me more productive. I want to share a few of them with you.<\/p>\n","protected":false},"author":642,"featured_media":224901,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[155],"tags":[294,12],"class_list":["post-224896","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-visual-studio","tag-extensions","tag-visual-studio"],"acf":[],"blog_post_summary":"

A few days ago, we announced the general availability of Visual Studio 2019. But I\u2019ve been using Visual Studio 2019 exclusively since the first internal build \u2013 long before the release of Preview 1 in December of 2018. During this time, there has been a lot of little features that have put a smile on my face and made me more productive. I want to share a few of them with you.<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts\/224896","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/users\/642"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/comments?post=224896"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts\/224896\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/media\/224901"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/media?parent=224896"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/categories?post=224896"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/tags?post=224896"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}