You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/ide/identifying-and-customizing-keyboard-shortcuts-in-visual-studio.md
+13-1Lines changed: 13 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Identify and customize keyboard shortcuts
3
3
description: Learn how to identify keyboard shortcuts for Visual Studio commands, customize those shortcuts, and export them for others to use.
4
-
ms.date: 02/05/2025
4
+
ms.date: 05/07/2026
5
5
ms.topic: how-to
6
6
f1_keywords:
7
7
- VS.ToolsOptionsPages.Environment.Keyboard
@@ -111,6 +111,17 @@ You can share your custom keyboard shortcuts by exporting them to a file and the
111
111
112
112
1. In the **What do you want to name your settings file** and **Store my settings file in this directory** boxes, either leave the default values or specify different values, and then choose **Finish**.
113
113
114
+
:::moniker range="visualstudio"
115
+
> [!NOTE]
116
+
> By default, your shortcuts are saved in a file in the following location:
> In the current version of Visual Studio, the `1x.0_xxxxxxxx` folder would start with the numerals 18.0 followed by a set of alphanumeric characters that are specific to your installation. Similarly, for Visual Studio 2022, the folder would start with the numerals 17.0.
121
+
>
122
+
> The name of the file itself reflects the date when you exported the settings, and the extension is *.vssettings*.
123
+
:::moniker-end
124
+
:::moniker range="<=vs-2022"
114
125
> [!NOTE]
115
126
> By default, your shortcuts are saved in a file in the following location:
116
127
>
@@ -119,6 +130,7 @@ You can share your custom keyboard shortcuts by exporting them to a file and the
119
130
> For Visual Studio 2022, the `1x.0_xxxxxxxx` folder would start with the numerals 17.0 followed by a set of alphanumeric characters that are specific to your installation. Similarly, for Visual Studio 2019, the folder would start with the numerals 16.0.
120
131
>
121
132
> The name of the file itself reflects the date when you exported the settings, and the extension is *.vssettings*.
description: Manage application settings that aren't included in the application code but are needed at runtime with the Visual Studio IDE.
4
-
ms.date: 10/02/2024
4
+
ms.date: 05/08/2026
5
5
ms.topic: how-to
6
6
f1_keywords:
7
7
- msvse_settingsdesigner.err.nameblank
@@ -16,7 +16,7 @@ ms.custom:
16
16
- awp-ai
17
17
#customer intent: As a developer, I want to use application settings to store information that isn't included in the application code at runtime.
18
18
---
19
-
# Manage application settings (.NET)
19
+
# Manage application settings (.NET Framework)
20
20
21
21
Application settings enable you to store application information dynamically. With application settings, you can use a client computer to store information that shouldn't be included in the application code at runtime. Application settings can include connection strings, user preferences, and more.
Copy file name to clipboardExpand all lines: docs/ide/using-intellisense.md
+12-2Lines changed: 12 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Use IntelliSense for quick information & completion
3
3
description: Explore how to work with IntelliSense features in Visual Studio, including List Members, Parameter Info, Quick Info, and Complete Word.
4
-
ms.date: 3/19/2026
4
+
ms.date: 5/5/2026
5
5
ms.topic: concept-article
6
6
helpviewer_keywords:
7
7
- Quick info
@@ -11,7 +11,7 @@ helpviewer_keywords:
11
11
- IntelliSense [Visual Studio]
12
12
author: ghogen
13
13
ms.author: ghogen
14
-
14
+
ms.custom: awp-ai
15
15
ms.subservice: general-ide
16
16
---
17
17
# IntelliSense in Visual Studio
@@ -26,8 +26,18 @@ These features include:
26
26
27
27
Many aspects of IntelliSense are language-specific. For more information about IntelliSense for different languages, see the articles listed in the [Related content](#related-content) section.
28
28
29
+
::: moniker range=">=visualstudio"
30
+
31
+
In addition to IntelliSense, Visual Studio offers AI-powered code completions through GitHub Copilot. Copilot inline suggestions work alongside IntelliSense to provide whole-line and multi-line completions. When IntelliSense is active, Copilot completions are temporarily suppressed so you can focus on the IntelliSense list. Once you dismiss or commit the IntelliSense selection, Copilot completions resume automatically. To learn more, see [Get started with GitHub Copilot completions](visual-studio-github-copilot-extension.md).
32
+
33
+
::: moniker-end
34
+
35
+
::: moniker range="<= vs-2022"
36
+
29
37
In addition to IntelliSense, Visual Studio offers AI-powered code completions through GitHub Copilot. Copilot inline suggestions work alongside IntelliSense to provide whole-line and multi-line completions. To learn more, see [Get started with GitHub Copilot completions](visual-studio-github-copilot-extension.md).
30
38
39
+
::: moniker-end
40
+
31
41
## List Members
32
42
33
43
A list of valid members from a type or namespace appears after you type a trigger character, such as a period (`.`) in managed code or `::` in C++. If you continue typing characters, the list filters to include only the members that begin with those characters or where the beginning of *any* word within the name starts with those characters. IntelliSense also performs *camel case* matching, so you can type just the first letter of each camel-cased word in the member name to see the matches.
WhenIntelliSenseisactive (forexample, when the member list or parameter info appears), Copilot completions are temporarily suppressed so you can focus on the IntelliSense list without distraction. Once you dismiss or commit the IntelliSense selection, Copilot completions resume automatically. This is the default behavior and requires no configuration.
Copy file name to clipboardExpand all lines: docs/ide/writing-code-in-the-code-and-text-editor.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Explore code editor features
3
3
description: Learn about the features that the code editor in Visual Studio provides to make it easier for you to write and manage your code and text.
4
-
ms.date: 02/05/2025
4
+
ms.date: 05/07/2026
5
5
ms.topic: concept-article
6
6
helpviewer_keywords:
7
7
- code, editing [Visual Studio]
@@ -26,11 +26,11 @@ The different Visual Studio languages offer different sets of features, and in s
26
26
27
27
|Feature|Description|
28
28
|-|-|
29
-
|Syntax Coloring|Some syntax elements of code and markup files are colored differently to distinguish them. For example, keywords (such as `using` in C# and `Imports` in Visual Basic) are one color, but types (such as `Console` and `Uri`) are another color. Other syntax elements are also colorized, such as string literals and comments. C++ uses color to differentiate among types, enumerations, and macros, among other tokens.<br><br> You can see the default color for each type, and you can change the color for any specific syntax element in the [Fonts and Colors, Environment, Options dialog box](../ide/reference/fonts-and-colors-environment-options-dialog-box.md), which you can open from the **Tools** menu.|
29
+
|Syntax Coloring|Some syntax elements of code and markup files are colored differently to distinguish them. For example, keywords (such as `using` in C# and `Imports` in Visual Basic) are one color, but types (such as `Console` and `Uri`) are another color. Other syntax elements are also colorized, such as string literals and comments. C++ uses color to differentiate among types, enumerations, and macros, among other tokens.<br><br> You can see the default color for each type, and you can change the color for any specific syntax element in the Fonts and Colors section of the Visual Studio settings pages, which you can open from the **Tools** menu. See [Customize environment options for fonts and colors](fonts-and-colors-environment-options-dialog-box.md).|
30
30
|Error and Warning Marks|As you add code and build your solution, you might see (a) different-colored wavy underlines known as squiggles or (b) light bulbs appearing in your code. Red squiggles denote syntax errors, blue denotes compiler errors, green denotes warnings, and purple denotes other types of errors. [Quick Actions](../ide/quick-actions.md) suggest fixes for problems and make it easy to apply the fix.<br><br> You can see the default color for each error and warning squiggle in the **Tools** > **Options** > **Environment** > **Fonts and Colors** dialog box. Under **Display items**, look for **Syntax Error**, **Compiler Error**, **Warning**, and **Other Error**.|
31
31
|Brace Matching|When the insertion point is placed on an open brace in a code file, both it and the closing brace are highlighted. This feature gives you immediate feedback on misplaced or missing braces. You can turn brace matching on or off with the **Automatic delimiter highlighting** setting (**Tools** > **Options** > **Text Editor**). You can change the highlight color in **Tools** > **Options** > **Environment** > **Fonts and Colors**. Look for **Brace Matching (Highlight)** or **Brace Matching (Rectangle)**.|
32
-
|Auto Surround|With Visual Studio 2022 version 17.9 and later, you can automatically surround a selection with matching delimiters when using double quotes (`""`), single quotes (`''`), brackets (`()`, `{}`, `[]`), or any delimiters supported by the file's language. When you add an opening delimiter (`"`, `'`, `(`) to a selection in your code file, the matching closing delimiter is automatically placed around the selection.<br><br>You can turn auto surround on or off with the **Automatically surround selections when typing quotes or brackets** setting in the **Display** section of the **Tools** > **Options** > **Text Editor** page.|
33
-
|Structure Visualizer|Dotted lines connect matching braces in code files, making it easier to see opening and closing brace pairs. This feature can help you find code in your codebase more quickly. You can turn these lines on or off with the **Show structure guidelines** in the **Display** section of the **Tools** > **Options** > **Text Editor** > **General** page.|
32
+
|Auto Surround|You can automatically surround a selection with matching delimiters when using double quotes (`""`), single quotes (`''`), brackets (`()`, `{}`, `[]`), or any delimiters supported by the file's language. When you add an opening delimiter (`"`, `'`, `(`) to a selection in your code file, the matching closing delimiter is automatically placed around the selection.<br><br>You can turn auto surround on or off with the **Automatically surround selections when typing quotes or brackets** setting in the **Display** section of the **Tools** > **Options** > **Text Editor** page.|
33
+
|Structure Visualizer|Dotted lines connect matching braces in code files, making it easier to see opening and closing brace pairs. This feature can help you find code in your codebase more quickly. You can turn these lines on or off with the **Show structure guide lines** in the **Display** section of the **Tools** > **Options** > **Text Editor** > **General** page.|
34
34
|Line Numbers|Line numbers can be displayed in the left margin of the code window. They aren't displayed by default. You can turn on this option in the **Text Editor All Languages** settings (**Tools** > **Options** > **Text Editor** > **All Languages**). You can display line numbers for individual programming languages by changing the settings for those languages (**Tools** > **Options** > **Text Editor** > **\<language>**). For line numbers to print, you must select **Include line numbers** in the **Print** dialog box.|
35
35
|Change Tracking|The color of the left margin allows you to keep track of the changes you made in a file. Changes you made since the file was opened but not saved are denoted by a yellow bar on the left margin (known as the selection margin). After you save the changes (but before closing the file), the bar turns green. If you undo a change after you save the file, the bar turns orange. To turn this feature off and on, change the **Track changes** option in the **Text Editor** settings (**Tools** > **Options** > **Text Editor**).|
36
36
|Selecting Code and Text|You can select text either in the standard continuous stream mode or in box mode, in which you select a rectangular portion of text instead of a set of lines. To make a selection in box mode, press **Alt** as you drag the mouse over the selection, or press **Alt**+**Shift**+**\<arrow key>**. The selection includes all of the characters within the rectangle defined by the first character and the last character in the selection. Anything typed or pasted into the selected area is inserted at the same point on each line.|
@@ -111,7 +111,7 @@ To define new hotkeys or redefine existing hotkeys, go to **Tools** > **Options*
111
111
112
112
The bottom margin of the editor contains some customization controls.
113
113
114
-
You can easily change the default indentation style from tabs to spaces to vice versa by clicking on SPC or TAB. The actual number of spaces is configurable in **Tools** > **Options**, under **All Settings** > **Text Editor** > **All languages** > **Tabs**.
114
+
You can easily change the default indentation style from tabs to spaces to vice versa by clicking on SPC or TAB. The actual number of spaces is configurable in **Tools** > **Options**, under **All Settings** > **Languages** > **Defaults** > **Tabs**.
115
115
116
116
You can also change the default end-of-line codes from CR LF, the standard on Windows, to a different setting for better compatibility with other operating systems.
0 commit comments