Secret Productivity Tips for Visual Studio 2017
Tags: dotnet, aspnet, microsoft, visualstudio
Published: 2017-05-16 14:39:48

---
title: "Secret Productivity Tips for Visual Studio 2017"
published: false
description: Microsoft's latest version of their flagship IDE has all sorts of incredible features, but many of them may be hidden by default. This post introduces many of them and shows you how to make the most of your development experience.
tags: dotnet, aspnet, microsoft, visual-studio
cover_image: https://thepracticaldev.s3.amazonaws.com/i/2qplss95ytf3n80fk87g.jpg
published: true
---

_This was originally posted on [my blog](http://rion.io)._

I've written a few blog posts thus far regarding Visual Studio 2017, so I thought I would take some time to discuss of the features that were introduced in this latest version that might help your productivity, or that you just may find useful.

You'll notice that the title of this post mentions that they are "secret". This is because **all of these features are disabled by default**, so you'll need to enable them, either locally (per project) or globally, to take advantage.

##NuGet Package Suggestion for Unrecognized Types

![automatically import from nuget](https://thepracticaldev.s3.amazonaws.com/i/lisynn6qnlw7bgv1l33x.gif)

In my opinion, one of the most useful additions to Visual Studio 2017 was the Nuget-based Using Suggestion feature. This feature will recommend installing a specific NuGet package to handle resolving an unrecognized type that is encountered within the editor.

It can be enabled via:

- **Tools > Options > Text Editor > C# > Advanced > Suggest Usings for Types in Nuget Packages**

Again - a great feature to speed up your productivity and it sure beats wandering around NuGet or running off to manually download the packages.

##Query Syntax in Go To All (Ctrl+T)

![filtering query syntax](https://thepracticaldev.s3.amazonaws.com/i/wgidy6i5wyt31xuxmkbs.gif)

Another incredibly useful tool introduced within Visual Studio 2017 was query searching within the Go To All (Ctrl+T) search area. This allows you to now quickly search for any file / type / member / or symbol by prefacing your search using the following prefixes:

- **f {file}**

- **t {type}**

- **m {member}**

- **# {symbol}**

This can allow you to easily narrow your search within your solution and find exactly what you need fast.


##Full Solution Analysis

![errors, messages, and warnings for the entire solution](https://thepracticaldev.s3.amazonaws.com/i/6utmlypovbjd61j0doe7.PNG)

The Full Solution Analysis feature is one that could be helpful to see every error, message, and warning throughout your entire solution (and not just the files that are currently open). 

This feature can be enabled via: 

- **Tools > Options > Text Editor > C# > Advanced > Enable Full Solution Analysis**

If you are a stickler that can't stand seeing a non-empty Error List, then this is for you.

####Lightweight Solution Load

![loading projects on demand](https://thepracticaldev.s3.amazonaws.com/i/xkimuri8hwl70gln6v4t.gif)

Another great feature that can add quite a bit of zing to Visual Studio 2017 is Lightweight Solution Load. This feature will initially load the _minimal_ amount necessary for each project to have them functional within Visual Studio. Individual project files and dependencies will not be loaded or expanded until requested, so you only load what you will need.

This feature can be enabled in two ways; locally:

- **Right-click Project > Enable Lightweight Solution Load**


Or globally (for all projects):

- **Tools > Options > Projects and Solutions > General > Lightweight Solution Load**

It's great for large solutions with multiple projects that maybe aren't all going to be touched for most scenarios or just if you just want  Visual Studio to open up a project faster than normal.

##Live Unit Testing


<a href='https://channel9.msdn.com/Events/Connect/2016/171/player' target='_blank'><img src='https://thepracticaldev.s3.amazonaws.com/i/rxi29qsvml8msj7zaojj.PNG' /></a>

Live Unit Testing was one of the features that was touted during the release of Visual Studio 2017, but it isn't actually enabled by default. This feature will figure out which unit tests are affected by any code changes and the tests will be automatically run. Additionally, it will decorate your code using icons to indicate which code is covered and the status of the test covering that code.

This feature can be enabled in two ways; locally:

- **Test > Live Unit Testing > Start**

Or globally (for all projects):

- **Options > Live Unit Testing**

Live Unit Testing is super handy for not only seeing what tests are passing and failing, but for examining code coverage as well. This feature is also highly configurable and will allow you to include / exclude specific tests, define the number of threads you want to dedicate to it, configure when the tests are run, and much more.

##EditorConfig Style Enforcement

![update-editor-styles](https://thepracticaldev.s3.amazonaws.com/i/90dhch671o6cf74pl7b6.gif)

Visual Studio 2017 adds support for [.editorconfig](http://editorconfig.org/) files within projects to help provide coding style recommendations, which can be useful for large development teams looking to maintain a consistent style across their code base. 

You may notice that the ellipses can be incredibly difficult to notice, especially if you are on the dark side. This can easily be adjusted within the IDE to make them far more visible from:

- **Tools > Options > Environment > Fonts and Colors > Suggestion Ellipsis**

You can then configure the color to make it "pop" out a bit more :

![styled suggestions](https://thepracticaldev.s3.amazonaws.com/i/x9q9t1dzr3743cxmle0s.PNG)

While this feature _is_ enabled by default (if an .editorconfig file is present), you can make the process of editing it much easier through Mads Kristensen's [EditorConfig extension](https://marketplace.visualstudio.com/items?itemName=MadsKristensen.EditorConfig), which can be downloaded and will provide full autocompletion, syntax highlighting, and much more.

##Keyboard Shortcuts

With many of the new additions and features that were added to Visual Studio 2017, you might be inclined to consider dropping support  for the heavyweight Resharper extension to see how vanilla Visual Studio works at this point. Or if you are a developer coming from another editor such as IntelliJ, Eclipse, you are probably pretty accustomed to the keyboard shortcuts from those tools. Well, there's an extension that has you covered.

[Justin Clarebert](https://twitter.com/justcla78), a member of the Visual Studio team released the [HotKeys Keyboard Shortcuts extension](https://marketplace.visualstudio.com/items?itemName=JustinClareburtMSFT.HotKeys2017-KeyboardShortcuts), which allows you to easily configure Visual Studio 2017 to use the keyboard shortcuts from those other popular editors and tools, giving you the productivity you are accustomed to within a new environment.

Okay. So this is another feature that _isn't_ directly built in to Visual Studio 2017, but it's too big of a productivity enhancer to leave off this list (and since it's not built it, I suppose it still qualifies as a "secret").


##In Closing

Hopefully, this list introduced you to a few features that you may have not been aware of within Visual Studio 2017 (and if you were, hopefully it showed you how to go about enabling it).