Repo sync for protected branch

docs/ide/default-keyboard-shortcuts-in-visual-studio.md

@@ -1,7 +1,7 @@
 ---
 title: Keyboard shortcuts
 description: Learn about the default keyboard shortcuts in Visual Studio that allow you to access a variety of commands and windows.
-ms.date: 04/27/2026
+ms.date: 06/26/2026
 ms.topic: reference
 helpviewer_keywords:
 - shortcut keys [Visual Studio], keyboard binding schemes
@@ -111,7 +111,7 @@ All shortcuts in this section apply globally unless otherwise specified. The *Gl
 |Line down extend column|**Shift+Alt+Down Arrow** [Text Editor]| Edit.LineDownExtendColumn |
 |Line open above|**Ctrl+Enter** [Text Editor]| Edit.LineOpenAbove |
 |List members|**Ctrl+J** [Text Editor, Workflow Designer]<br /><br />or **Ctrl+K, Ctrl+L** [Workflow Designer]<br /><br />or **Ctrl+K, L** [Workflow Designer]| Edit.ListMembers |
-|Navigate to|**Ctrl+,**| Edit.NavigateTo |
+|Navigate to|**Ctrl+P**<br /><br />or **Ctrl+,**<br /><br />or **Ctrl+T**| Edit.NavigateTo |
 |Open file|**Ctrl+Shift+G**| Edit.OpenFile |
 |Overtype mode|**Insert** [Text Editor]| Edit.OvertypeMode |
 |Parameter info|**Ctrl+Shift+Spacebar** [Text Editor, Workflow Designer]<br /><br />or **Ctrl+K, Ctrl+P** [Workflow Designer]<br /><br />or **Ctrl+K, P** [Workflow Designer]| Edit.ParameterInfo |
@@ -120,7 +120,6 @@ All shortcuts in this section apply globally unless otherwise specified. The *Gl
 |Redo|**Ctrl+Y**<br /><br />or **Shift+Alt+Backspace**<br /><br />or **Ctrl+Shift+Z**| Edit.Redo |
 |Replace|**Ctrl+H**| Edit.Replace |
 |Select all|**Ctrl+A**| Edit.SelectAll |
-|Select current word|**Ctrl+W** [Text Editor]| Edit.SelectCurrentWord |
 |Selection cancel|**Esc** [Text Editor, Report Designer, Settings Designer, Windows Forms Designer, Managed Resources Editor]| Edit.SelectionCancel |
 |Remove and sort usings|**Ctrl+R, Ctrl+G** [Text Editor]| EditorContextMenus.CodeWindow.RemoveAndSort |
 |Surround with|**Ctrl+K, Ctrl+S** <br>(available only in Visual Studio 2019 and earlier)| Edit.SurroundWith |
@@ -196,11 +195,14 @@ All shortcuts in this section apply globally unless otherwise specified. The *Gl
 |Commands|Keyboard shortcuts [Special contexts]|Command ID|
 |-|-|-|
 |Activate document window|**Esc**| Window.ActivateDocumentWindow |
-|Close document window|**Ctrl+F4**| Window.CloseDocumentWindow |
+|Close document window|**Ctrl+W**<br /><br />or **Ctrl+F4**| Window.CloseDocumentWindow |
 |Next document window|**Ctrl+F6**| Window.NextDocumentWindow |
 |Next document window nav|**Ctrl+Tab**| Window.NextDocumentWindowNav |
 |Next split pane|**F6**| Window.NextSplitPane |
 
+> [!NOTE]
+> In the Visual C# profile, **Ctrl+W** isn't assigned to **Window.CloseDocumentWindow** by default. If you want to use **Ctrl+W** to close tabs, go to **Tools** > **Options** > **Environment** > **Keyboard** to customize the shortcut. For more information, see [customize a keyboard shortcut](identifying-and-customizing-keyboard-shortcuts-in-visual-studio.md#customize-a-keyboard-shortcut).
+
 ## Global shortcuts
 
 These keyboard shortcuts are *global*, which means that you can use them when any Visual Studio window has focus.
@@ -370,7 +372,7 @@ These keyboard shortcuts are *global*, which means that you can use them when an
 |Find previous selected|**Ctrl+Shift+F3**| Edit.FindPreviousSelected |
 |Generate method|**Ctrl+K, Ctrl+M**| Edit.GenerateMethod |
 |Go to|**Ctrl+G**| Edit.GoTo |
-|Go to all|**Ctrl+,** or **Ctrl+T**| Edit.GoToAll |
+|Go to all|**Ctrl+P** or **Ctrl+,** or **Ctrl+T**| Edit.GoToAll |
 |Go to declaration|**Ctrl+F12**| Edit.GoToDeclaration |
 |Go to definition|**F12**| Edit.GoToDefinition |
 |Go to member|**Ctrl+1, Ctrl+M** or **Ctrl+1, M** or **Alt+\\**| Edit.GoToMember |
@@ -612,7 +614,7 @@ These keyboard shortcuts are *global*, which means that you can use them when an
 |-|-|-|
 |Activate document window|**Esc**| Window.ActivateDocumentWindow |
 |Add tab to selection|**Ctrl+Shift+Alt+Space**| Window.AddTabtoSelection |
-|Close document window|**Ctrl+F4**| Window.CloseDocumentWindow |
+|Close document window|**Ctrl+W**<br /><br />or **Ctrl+F4**| Window.CloseDocumentWindow |
 |Close tool window|**Shift+Esc**| Window.CloseToolWindow |
 |Keep tab open|**Ctrl+Alt+Home**| Window.KeepTabOpen |
 |Move  to navigation bar|**Ctrl+F2**| Window.MovetoNavigationBar |
@@ -1163,7 +1165,7 @@ The shortcuts specific to this context are:
 |Reverse incremental search| **Ctrl+Shift+I** | Edit.ReverseIncrementalSearch |
 |Scroll line down| **Ctrl+Down Arrow** | Edit.ScrollLineDown |
 |Scroll line up| **Ctrl+Up Arrow** | Edit.ScrollLineUp |
-|Select current word| **Ctrl+W** | Edit.SelectCurrentWord |
+|Select current word| None | Edit.SelectCurrentWord |
 |Selection cancel| **Escape** | Edit.SelectionCancel |
 |Select to last go back| **Ctrl+=** | Edit.SelectToLastGoBack |
 |Show code lens menu| **Ctrl+K, Ctrl+\`** | Edit.ShowCodeLensMenu |

docs/ide/quickstart-ide-orientation.md

@@ -145,7 +145,7 @@ To explore Visual Studio's features, let's create a new project.
 
     :::image type="content" source="media/vs-2022/quickstart-ide-error-list.png" alt-text="Screenshot of the Error List in Visual Studio." lightbox="media/vs-2022/quickstart-ide-error-list.png":::
 
-* The **Search** box at the top is a quick and easy way to find just about anything in Visual Studio. You can search for features using **Feature Search** (`Ctrl + Q`) or search your code elements, such as files and symbols, using **Code Search**(`Ctrl+P`). For example, to open a **Terminal** window, just search for it and open from the search results. The built-in terminal is opened and is ready for commands.
+* The **Search** box at the top is a quick and easy way to find just about anything in Visual Studio. You can search for features using **Feature Search** (`Ctrl + Shift + P`, `Ctrl + ,`, or `Ctrl + Q`) or search your code elements, such as files and symbols, using **Code Search** (`Ctrl + P`). For example, to open a **Terminal** window, just search for it and open from the search results. The built-in terminal is opened and is ready for commands.
 
     :::image type="content" source="media/visualstudio/ide-tour-toolbar-search-box.png" alt-text="Screenshot of the Search box in Visual Studio." lightbox="media/visualstudio/ide-tour-toolbar-search-box.png":::
 
@@ -184,7 +184,7 @@ To explore Visual Studio's features, let's create a new project.
 
     :::image type="content" source="media/vs-2022/quickstart-ide-error-list.png" alt-text="Screenshot of the Error List in Visual Studio 2022.":::
 
-* The **Search** box at the top is a quick and easy way to find just about anything in Visual Studio. You can search for features using **Feature Search** (`Ctrl + Q`) or search your code elements, such as files and symbols, using **Code Search**(`Ctrl+T`). For example, to open a **Terminal** window, just search for it and open from the search results. The built-in terminal is opened and is ready for commands.
+* The **Search** box at the top is a quick and easy way to find just about anything in Visual Studio. You can search for features using **Feature Search** (`Ctrl + Shift + P`, `Ctrl + ,` or `Ctrl + Q`) or search your code elements, such as files and symbols, using **Code Search** (`Ctrl + P` or `Ctrl + T`). For example, to open a **Terminal** window, just search for it and open from the search results. The built-in terminal is opened and is ready for commands.
 
     :::image type="content" source="media/vs-2022/ide-tour-toolbar-search-box.png" alt-text="Screenshot of the Search box in Visual Studio 2022.":::
 

docs/ide/visual-studio-search.md

@@ -1,7 +1,7 @@
 ---
 title: Use Visual Studio search to find code & do queries
 description: Explore the Visual Studio search feature and discover how to find settings, menus, code, and work with filters, queries, and more.
-ms.date: 9/16/2025
+ms.date: 06/26/2026
 ms.topic: how-to
 helpviewer_keywords:
 - environments [Visual Studio], navigation
@@ -155,7 +155,7 @@ In Visual Studio 17.13 and later, when you open Code Search without a query, you
 
 ### Keyboard shortcuts for search
 
-You can use the **Ctrl**+**Q** keyboard shortcut for feature searches, and the **Ctrl**+**T** keyboard shortcut for code searches. 
+Use the **Ctrl**+**Shift**+**P** or **Ctrl**+**Q** keyboard shortcut for feature searches. Use the **Ctrl**+**P** or **Ctrl**+**T** keyboard shortcut for code searches.
 
 ### Filters for Code Search queries
 

docs/install/import-export-installation-configurations.md

@@ -2,7 +2,7 @@
 title: Import or export installation configurations
 titleSuffix: ''
 description: "Learn how to import, export, and share your Visual Studio installation configuration by using a .vsconfig file."
-ms.date: 03/19/2026
+ms.date: 06/26/2026
 ms.topic: how-to
 helpviewer_keywords:
 - import installation configuration
@@ -62,6 +62,11 @@ You can programmatically export a configuration file of a particular Visual Stud
 
 You can import an installation configuration file into a previously installed instance of Visual Studio, or you can use it to initialize a new installation of Visual Studio. Importing a configuration file into Visual Studio installs anything listed in the config file that's not already installed.
 
+How you apply a *.vsconfig* file depends on whether Visual Studio is already installed:
+
+- If Visual Studio isn't installed yet, use the edition bootstrapper (for example, `vs_professional.exe`) with `--config`.
+- If Visual Studio is already installed, use `modify` with `--config` (for example, `setup.exe modify`).
+
 ### Use the Visual Studio Installer UI
 
 When you're ready to import an installation configuration file, follow these steps.
@@ -74,14 +79,57 @@ When you're ready to import an installation configuration file, follow these ste
 
 1. Verify that your selections are accurate, and then choose **Modify**.
 
+### Programmatically use a configuration file for a new installation
+
+To use a *.vsconfig* file during a first-time installation, [download the correct bootstrapper that matches the version and edition that you want](install-visual-studio.md#step-2---determine-which-version-and-edition-of-visual-studio-to-install) (for example, `vs_professional.exe`). Then open an Administrator Command Prompt and run the bootstrapper with the `--config` parameter.
+
+```shell
+vs_professional.exe --config "C:\myconfig.vsconfig" --passive --wait
+```
+
+If you want to set the install location explicitly, include `--installPath`.
+
+:::moniker range="visualstudio"
+
+```shell
+vs_professional.exe --installPath "C:\Program Files\Microsoft Visual Studio\18\Professional" --config "C:\myconfig.vsconfig" --passive --wait
+```
+
+:::moniker-end
+
+:::moniker range="vs-2022"
+
+```shell
+vs_professional.exe --installPath "C:\Program Files\Microsoft Visual Studio\2022\Professional" --config "C:\myconfig.vsconfig" --passive --wait
+```
+
+:::moniker-end
+
+> [!IMPORTANT]
+> For a first-time installation, use the edition bootstrapper (`vs_professional.exe`, `vs_enterprise.exe`, and so on), not `setup.exe modify`.
+>
+> If your *.vsconfig* file includes extensions and you're running in `--passive` or `--quiet` mode, include `--allowUnsignedExtensions`.
+
 ### Programmatically use a configuration file to add components to an existing installation
 
-You can use the `--config` parameter to either initialize or modify an existing installation and add components. The following example uses the installer on the client machine to `modify` an existing installation.
+You can use the `--config` parameter with `modify` to add components to an existing installation. The following example uses the installer on the client machine to `modify` an existing installation.
+
+:::moniker range="visualstudio"
+
+```shell
+"C:\Program Files (x86)\Microsoft Visual Studio\Installer\setup.exe" modify --installPath "C:\Program Files\Microsoft Visual Studio\18\Professional" --config "C:\myconfig.vsconfig" --passive --allowUnsignedExtensions
+```
+
+:::moniker-end
+
+:::moniker range="vs-2022"
 
 ```shell
 "C:\Program Files (x86)\Microsoft Visual Studio\Installer\setup.exe" modify --installPath "C:\Program Files\Microsoft Visual Studio\2022\Professional" --config "C:\myconfig.vsconfig" --passive --allowUnsignedExtensions
 ```
 
+:::moniker-end
+
 > [!NOTE]
 > To add components to an existing installation by using a *.vsconfig* file, you need to use `modify` and **not** `update`. The `update` command just updates existing installed components to the latest version. To learn more about the different installer operations, refer to the [Install Visual Studio from the command line](use-command-line-parameters-to-install-visual-studio.md) documentation.
 
@@ -101,7 +149,6 @@ If you save a *.vsconfig* file into your solution root directory and then open a
 > [!NOTE]
 > If your *.vsconfig* file contains extensions, then currently, only those extensions that are hosted on the [Visual Studio Marketplace](https://marketplace.visualstudio.com/) trigger the automatic *is-missing* detection and installation. If you would like this logic to include extensions that were installed from a non-Marketplace location, please [provide details about your scenario here](https://developercommunity.visualstudio.com/t/post/10607414).
 
-
 :::moniker range="visualstudio"
 :::image type="content" source="media/visualstudio/solution-explorer-config-file.png" alt-text="Screenshot of Solution Explorer suggesting additional components.":::
 :::moniker-end