From f9a505aeafa2b421d415a472a2fcba9d2c6b1e43 Mon Sep 17 00:00:00 2001 From: Takashi Takebayashi Date: Wed, 22 Jan 2025 17:25:40 +0900 Subject: [PATCH] Fix typo Visual studio -> Visual Studio --- ...-dot-pdb-and-source-files-in-the-visual-studio-debugger.md | 2 +- docs/extensibility/installing-the-visual-studio-sdk.md | 4 ++-- docs/extensibility/the-experimental-instance.md | 2 +- ...ng-a-view-adornment-commands-and-settings-column-guides.md | 2 +- docs/install/update-visual-studio.md | 2 +- 5 files changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/debugger/specify-symbol-dot-pdb-and-source-files-in-the-visual-studio-debugger.md b/docs/debugger/specify-symbol-dot-pdb-and-source-files-in-the-visual-studio-debugger.md index c1c51a60b62..47614a8c330 100644 --- a/docs/debugger/specify-symbol-dot-pdb-and-source-files-in-the-visual-studio-debugger.md +++ b/docs/debugger/specify-symbol-dot-pdb-and-source-files-in-the-visual-studio-debugger.md @@ -151,7 +151,7 @@ On the **Tools** > **Options** > **Debugging** > **Symbols** page, you can: ::: moniker range=">= vs-2022" - Select **Automatically choose what module symbols to search for** (recommended) to allow - Visual studio to decide what symbols to search for and load. By default, Visual Studio + Visual Studio to decide what symbols to search for and load. By default, Visual Studio automatically loads symbols that were built by your opened solution, and loads any additional symbols that are needed to perform common debugging operations. This reduces the number of files that must be searched for and loaded by Visual Studio, which diff --git a/docs/extensibility/installing-the-visual-studio-sdk.md b/docs/extensibility/installing-the-visual-studio-sdk.md index c4bbf998650..96374ea6422 100644 --- a/docs/extensibility/installing-the-visual-studio-sdk.md +++ b/docs/extensibility/installing-the-visual-studio-sdk.md @@ -25,11 +25,11 @@ To install the Visual Studio SDK after completing your Visual Studio installatio If you open a solution with an extensibility project without first installing the VSSDK, you'll be prompted by an **Install Missing Feature** dialog to install the **Visual Studio extension development** workload: ::: moniker range="vs-2019" -:::image type="content" source="media/install-extension-development.png" alt-text="Screenshot showing the Visual studio dialog to Install extension development workload."::: +:::image type="content" source="media/install-extension-development.png" alt-text="Screenshot showing the Visual Studio dialog to Install extension development workload."::: ::: moniker-end ::: moniker range=">=vs-2022" -:::image type="content" source="media/vs-2022/install-extension-development.png" alt-text="Screenshot showing the Visual studio dialog to Install extension development workload."::: +:::image type="content" source="media/vs-2022/install-extension-development.png" alt-text="Screenshot showing the Visual Studio dialog to Install extension development workload."::: ::: moniker-end ## Install the Visual Studio SDK from the command line diff --git a/docs/extensibility/the-experimental-instance.md b/docs/extensibility/the-experimental-instance.md index 5ea5f490fcd..892c44ce9d8 100644 --- a/docs/extensibility/the-experimental-instance.md +++ b/docs/extensibility/the-experimental-instance.md @@ -20,7 +20,7 @@ To safeguard your Visual Studio development environment from untested applicatio If you want to start the experimental instance of Visual Studio outside a specific solution, run the following command at the command window: - "*\*\Common7\IDE\devenv.exe" /RootSuffix Exp + "*\*\Common7\IDE\devenv.exe" /RootSuffix Exp > [!NOTE] > The experimental instance is written to the registry under the `Exp` and `Exp_Config` nodes. For example the Visual Studio 2015 experimental registry area is diff --git a/docs/extensibility/walkthrough-creating-a-view-adornment-commands-and-settings-column-guides.md b/docs/extensibility/walkthrough-creating-a-view-adornment-commands-and-settings-column-guides.md index 71e4de0d29c..39d565e7cea 100644 --- a/docs/extensibility/walkthrough-creating-a-view-adornment-commands-and-settings-column-guides.md +++ b/docs/extensibility/walkthrough-creating-a-view-adornment-commands-and-settings-column-guides.md @@ -1163,7 +1163,7 @@ _addGuidelineCommand = ``` -You create an `OleMenuCommand`. Visual Studio uses the Microsoft Office command system. The key arguments when instantiating an `OleMenuCommand` is the function that implements the command (`AddColumnGuideExecuted`), the function to call when Visual Studio shows a menu with the command (`AddColumnGuideBeforeQueryStatus`), and the command ID. Visual studio calls the query status function before showing a command on a menu so that the command can make itself invisible or greyed out for a particular display of the menu (for example, disabling **Copy** if there's no selection), change its icon, or even change its name (for example, from Add Something to Remove Something), and so on. The command ID must match a command ID declared in the *.vsct* file. The strings for the command set and the column guides add command must match between the *.vsct* file and the *ColumnGuideCommands.cs*. +You create an `OleMenuCommand`. Visual Studio uses the Microsoft Office command system. The key arguments when instantiating an `OleMenuCommand` is the function that implements the command (`AddColumnGuideExecuted`), the function to call when Visual Studio shows a menu with the command (`AddColumnGuideBeforeQueryStatus`), and the command ID. Visual Studio calls the query status function before showing a command on a menu so that the command can make itself invisible or greyed out for a particular display of the menu (for example, disabling **Copy** if there's no selection), change its icon, or even change its name (for example, from Add Something to Remove Something), and so on. The command ID must match a command ID declared in the *.vsct* file. The strings for the command set and the column guides add command must match between the *.vsct* file and the *ColumnGuideCommands.cs*. The following line provides assistance for when users invoke the command via the Command Window (explained below): diff --git a/docs/install/update-visual-studio.md b/docs/install/update-visual-studio.md index f4d33c181cf..416cfaa0723 100644 --- a/docs/install/update-visual-studio.md +++ b/docs/install/update-visual-studio.md @@ -209,7 +209,7 @@ There are two ways to bring up the Update Settings dialog, which allows you to m ![Screenshot showing the Updates settings in the Update available dialog in the IDE.](media/vs-2022/invoke-update-settings-in-the-ide.png) -The **Update Settings** dialog will look something like this. In this example, the Visual studio instance is using the LTSC 17.8 channel. +The **Update Settings** dialog will look something like this. In this example, the Visual Studio instance is using the LTSC 17.8 channel. ![Screenshot showing the Updates settings dialog in the Visual Studio 2022 IDE.](media/vs-2022/update-setting-dialog-one.png)