ReSharper 2016.3 Help

Smart Completion

ReSharper | Edit | Smart Code Completion
Ctrl+Shift+Space
ReSharper_CompleteCodeSmart

This command filters the list of types, methods, and variables to match the expected type of an expression. It works anywhere as long as ReSharper can determine the expected type of the expression, for example, right-hand sides of assignments, variable initializers, or return statements. If several return types are possible, ReSharper detects the most recently used symbol of an applicable type and automatically selects it in the lookup list. Smart Completion can also suggest creating anonymous delegates, lambda expressions, and regular methods, as well as local variables for out parameters. In addition to that, in object initializers, Smart Completion suggests fields/properties that were not yet assigned a value.

By default, smart completion items are included in the suggestion lists of automatic and basic completion. If you want to change the default behavior, use the corresponding controls on the Environment | IntelliSense | Completion Behavior page of ReSharper options.

To invoke smart completion

  1. Place the caret at the position where you're going to type your code.
  2. Press Ctrl+Shift+Space.
  3. Select a suggestion from the list and press Enter or start typing the initial letters of the identifier or its CamelHumps abbreviation to narrow down the list of suggestions.

You can also invoke smart completion on an existing identifier. In this case, there are two ways to apply the selected completion suggestion; press Enter to insert it and leave the existing item or press Tab to replace the existing item (If necessary, you can change the default shortcuts on the Environment | IntelliSense | Completion Characters page of ReSharper options).

Examples of smart completion

You can use the following examples to get an idea of how smart completion works with various code items:

After a return statement

/help/img/dotnet/2016.3/Coding_Assistance__Code_Completion__Smart__smart_return.png

In the right-hand side of assignments

/help/img/dotnet/2016.3/Coding_Assistance__Code_Completion__Smart__smart_dot.png

In cast expressions

Before:

/help/img/dotnet/2016.3/Coding_Assistance__Code_Completion__Smart__smart_cast_01.png
After launching Smart Completion (since there's a single option in this case, ReSharper inserts the expected type without displaying a drop-down list):
/help/img/dotnet/2016.3/Coding_Assistance__Code_Completion__Smart__smart_cast_02.png

In object initializers

ReSharper provides Smart Completion for setting properties in object initializers that were not previously set for a particular object:

/help/img/dotnet/2016.3/Coding_Assistance__Code_Completion__Smart__object_initializer.png

In lambda expressions

In addition to traditional anonymous and named methods, Smart Completion readily generates lambda-expression syntax:

/help/img/dotnet/2016.3/Coding_Assistance__Code_Completion__Smart__lambdas.png

Creating a local variable in place of an out parameter

/help/img/dotnet/2016.3/Coding_Assistance__Code_Completion__Smart__local_variable.png

Using CamelHumps

/help/img/dotnet/2016.3/Coding_Assistance__Code_Completion__Smart__CamelHumps.png

This feature is supported in the following languages/technologies:

C# VB.NET C++ HTML ASPX Razor JavaScript TypeScript CSS XML XAML RESX Build Scripts Protobuf JSON
/help/img/dotnet/2016.3/check.svg /help/img/dotnet/2016.3/check.svg /help/img/dotnet/2016.3/cross.svg /help/img/dotnet/2016.3/cross.svg /help/img/dotnet/2016.3/check.svg /help/img/dotnet/2016.3/check.svg /help/img/dotnet/2016.3/cross.svg /help/img/dotnet/2016.3/cross.svg /help/img/dotnet/2016.3/cross.svg /help/img/dotnet/2016.3/cross.svg /help/img/dotnet/2016.3/check.svg /help/img/dotnet/2016.3/cross.svg /help/img/dotnet/2016.3/cross.svg /help/img/dotnet/2016.3/cross.svg /help/img/dotnet/2016.3/cross.svg

The instructions and examples given here address the use of the feature in C#. For details specific to other languages, see corresponding topics in the ReSharper by Language section.

See Also

Last modified: 15 February 2017