diff --git a/docs/code-quality/install-roslyn-analyzers.md b/docs/code-quality/install-roslyn-analyzers.md index e576c927974..60242a1afad 100644 --- a/docs/code-quality/install-roslyn-analyzers.md +++ b/docs/code-quality/install-roslyn-analyzers.md @@ -1,5 +1,5 @@ --- -title: Install external analyzers +title: Install External Analyzers description: Learn how to install external analyzers in Visual Studio. Install analyzers with NuGet analyzer packages and as a VSIX extension. author: mikadumont ms.author: midumont @@ -10,7 +10,7 @@ helpviewer_keywords: - code analysis, managed code - analyzers - Roslyn analyzers -ms.date: 03/25/2024 +ms.date: 05/15/2026 --- # Install external analyzers @@ -52,8 +52,18 @@ To install a Visual Studio Extension-based analyzer, follow these steps: The **VSIX Installer** dialog box opens. + ::: moniker range="visualstudio" + + ![Screenshot of VSIX Installer dialog in Visual Studio.](media/visualstudio/installer-code-analysis.png) + + ::: moniker-end + + ::: moniker range="vs-2022" + ![Screenshot that shows the VSIX Installer dialog box.](media/vsix-installer-code-analysis.png) + ::: moniker-end + 1. Select **Modify** to start the installation. 1. After a minute or two, the installation completes. Select **Close**. diff --git a/docs/code-quality/media/visualstudio/installer-code-analysis.png b/docs/code-quality/media/visualstudio/installer-code-analysis.png new file mode 100644 index 00000000000..5643d6b0c4d Binary files /dev/null and b/docs/code-quality/media/visualstudio/installer-code-analysis.png differ diff --git a/docs/ide/copilot-agent-mode.md b/docs/ide/copilot-agent-mode.md index 73f53f55829..beec644825d 100644 --- a/docs/ide/copilot-agent-mode.md +++ b/docs/ide/copilot-agent-mode.md @@ -1,7 +1,7 @@ --- title: Use Agent Mode description: Use the GitHub Copilot agent to iterate on code in Visual Studio by making code edits, running commands, and reading error/build context. -ms.date: 04/02/2026 +ms.date: 05/11/2026 ms.update-cycle: 180-days ms.topic: get-started author: RoseHJM @@ -128,7 +128,7 @@ Agent mode can use the following tools for responding to a request: - [Agent skills](copilot-agent-skills.md) that provide task-specific instructions > [!TIP] -> Visual Studio also includes built-in agents like @debug, @profiler, @test, and @vs that integrate with specific IDE features. You can also create custom agents for your team workflows. For more information, see [Use custom agents in GitHub Copilot](copilot-specialized-agents.md). +> Visual Studio also includes built-in agents like @debug, @profiler, @test, and @vs that integrate with specific IDE features. In agent mode, @debug can guide bug reproduction, instrumentation and telemetry collection, and fix validation. You can also create custom agents for your team workflows. For more information, see [Use custom agents in GitHub Copilot](copilot-specialized-agents.md). To view and manage the tools that are available in agent mode, select the **Tools** icon in the chat window. @@ -165,8 +165,19 @@ Once you enable the tool, Copilot uses it automatically when answering your ques Supported languages include C++, C#, Razor, and TypeScript, plus any other language for which you have a supported Language Server Protocol (LSP) extension installed. +For C++ projects, agent mode can also use C++ tools to navigate call and class hierarchies. For more information, see [C++ code editing tools](#c-code-editing-tools). + For best results, write clear prompts and use AI models that support tool-calling. For more information about model capabilities, see [AI model comparison (GitHub Docs)](https://docs.github.com/copilot/reference/ai-models/model-comparison). +### C++ code editing tools + +When C++ code editing tools are enabled in the **Tools** list in Copilot Chat, agent mode can use these Visual Studio-specific tools: + +- `get_symbol_call_hierarchy` to traverse call hierarchies +- `get_symbol_class_hierarchy` to navigate class and type hierarchies + +These tools help the agent reason over C++ relationships so it can make more precise navigation and editing decisions. To use these tools, install the **Desktop development with C++** workload. After these tools are available and enabled, agent mode uses them automatically when applicable. + :::moniker-end ## Manage tool approvals diff --git a/docs/ide/copilot-specialized-agents.md b/docs/ide/copilot-specialized-agents.md index cadc844ea42..2a8b111f5c8 100644 --- a/docs/ide/copilot-specialized-agents.md +++ b/docs/ide/copilot-specialized-agents.md @@ -1,7 +1,7 @@ --- title: Use custom agents in GitHub Copilot description: Learn about built-in agents for debugging, profiling, testing, and code modernization, and how to create custom agents for your team workflows. -ms.date: 04/21/2026 +ms.date: 05/11/2026 ms.topic: how-to author: mikejo5000 ms.author: mikejo @@ -43,12 +43,6 @@ You can access custom agents by using **@ syntax**: Type `@` followed by the age :::moniker-end -:::moniker range="vs-2022" - -:::image type="content" source="media/vs-2022/agent-picker.png" alt-text="Screenshot showing the agent picker with custom agents."::: - -:::moniker-end - ## Built-in agents Each built-in agent focuses on a specific developer workflow. These agents integrate with Visual Studio's native tooling in ways that a generic assistant can't. @@ -68,8 +62,13 @@ Each built-in agent focuses on a specific developer workflow. These agents integ | **@profiler** | Connects to Visual Studio's profiling infrastructure to identify bottlenecks and suggest targeted optimizations grounded in your codebase, not generic advice. | ::: moniker-end + :::moniker range="visualstudio" +## Cloud agents + +In Copilot Chat, you can start cloud-based agent sessions from the agent picker. A connected repository means you have a local solution open from a GitHub repository and you're signed in to GitHub in Visual Studio. These remote sessions are powered by the GitHub Copilot coding agent and can create repository issues and pull requests in that repository. + ### Use the @debugger agent The @debugger agent helps you diagnose errors systematically by analyzing your debugging context. It also supports an end-to-end agentic workflow that reproduces bugs, instruments your app with tracepoints and conditional breakpoints, and validates fixes using live runtime data. For more information, see [Agentic bug resolution with the Debugger Agent](../debugger/debug-with-copilot.md#agentic-bug-resolution-with-the-debugger-agent). @@ -106,10 +105,6 @@ The @test agent generates unit tests that match your project's testing framework For more comprehensive .NET testing support, see [GitHub Copilot testing for .NET](../test/github-copilot-test-dotnet-overview.md). -::: moniker-end - -:::moniker range="visualstudio" - ### Use the @modernize agent The @modernize agent helps with framework migrations and dependency upgrades for .NET and C++ projects. @@ -196,6 +191,15 @@ Tools extend what your custom agent can do. You can specify which tools the agen > [!IMPORTANT] > Tool names vary across GitHub Copilot platforms. Check the tools available in Visual Studio specifically to make sure your agent works as expected. Select the **Tools** icon in the chat window to see available tool names. +### Language-specific tools for C++ + +C++ code editing tools are generally available in agent mode. If the C++ workload is installed, your custom agent can use these Visual Studio-specific tool names in its `tools` array: + +- `get_symbol_call_hierarchy` for call hierarchy navigation +- `get_symbol_class_hierarchy` for class and type hierarchy navigation + +These tools give agents language-aware navigation for C++ and help improve precision when analyzing and editing C++ code. + ### Connect to external sources with MCP By using [MCP servers](mcp-servers.md), your custom agents can access external knowledge sources such as: diff --git a/docs/ide/default-keyboard-shortcuts-in-visual-studio.md b/docs/ide/default-keyboard-shortcuts-in-visual-studio.md index 7d1eb84dfbc..6a64c7e68f4 100644 --- a/docs/ide/default-keyboard-shortcuts-in-visual-studio.md +++ b/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: 3/26/2026 +ms.date: 04/27/2026 ms.topic: reference helpviewer_keywords: - shortcut keys [Visual Studio], keyboard binding schemes @@ -11,6 +11,7 @@ helpviewer_keywords: - keyboard shortcuts author: ghogen ms.author: ghogen +ms.custom: awp-ai ms.subservice: general-ide --- @@ -523,6 +524,9 @@ These keyboard shortcuts are *global*, which means that you can use them when an |Go to web access|**Ctrl+0** (zero), **Ctrl+A**

or

**Ctrl+0, A**| TeamFoundationContextMenus.Commands.GoToWebAccess | |Go to work items|**Ctrl+0** (zero), **Ctrl+W**

or

**Ctrl+0, W**| TeamFoundationContextMenus.Commands.GoToWorkItems | +> [!NOTE] +> The legacy Team Explorer work items experience is deprecated. Going forward, the **Go to work items** command no longer opens inside Visual Studio and instead opens work items in the web portal, where you'll find a modern, more consistent experience. This change aligns with updates introduced in Visual Studio 2019 and 2022 and ensures that all work item features are available through the web experience. For more information, see [work items in Visual Studio](https://devblogs.microsoft.com/devops/work-items-in-visual-studio/). + ### Test: global shortcuts |Commands|Keyboard shortcuts|Command ID| diff --git a/docs/ide/develop-code-in-visual-studio-without-projects-or-solutions.md b/docs/ide/develop-code-in-visual-studio-without-projects-or-solutions.md index 0c775955f37..b8541247800 100644 --- a/docs/ide/develop-code-in-visual-studio-without-projects-or-solutions.md +++ b/docs/ide/develop-code-in-visual-studio-without-projects-or-solutions.md @@ -1,7 +1,7 @@ --- title: Develop code without projects or solutions description: Develop code directly in Visual Studio without placing the code in a solution or project, and start working quickly with IntelliSense, search, debugging, and more. -ms.date: 11/7/2023 +ms.date: 04/27/2026 ms.topic: how-to helpviewer_keywords: - open folder [Visual Studio] @@ -9,6 +9,7 @@ helpviewer_keywords: - projects and solutions, develop code without author: Mikejo5000 ms.author: mikejo +ms.custom: awp-ai ms.subservice: general-ide --- @@ -83,6 +84,9 @@ As of Visual Studio 2019 [version 16.8](/visualstudio/releases/2019/release-note You can still use Team Explorer in Visual Studio 2022 and in Visual Studio 2019 [version 16.8](/visualstudio/releases/2019/release-notes/) and later. However, you might find it easier to use the new Git experience. For more information, see [How Visual Studio makes version control easy with Git](../version-control/git-with-visual-studio.md). +> [!NOTE] +> The legacy work items experience in Team Explorer is deprecated. Going forward, work items no longer open inside Visual Studio and instead open in the web portal, where you'll find a modern, more consistent experience. This change aligns with updates introduced in Visual Studio 2019 and 2022 and ensures that all work item features are available through the web experience. For more information, see [work items in Visual Studio](https://devblogs.microsoft.com/devops/work-items-in-visual-studio/). + 1. In Visual Studio, choose the **Team Explorer** tab to open **Team Explorer**. If you don't see the tab, open it from **View** > **Team Explorer**. 1. In Team Explorer, under the **Local Git Repositories** section, choose the **Clone** command and then paste the URL of the GitHub page into the text box. diff --git a/docs/ide/media/visualstudio/account-settings-filter-account-dialogs-tenants-filtered-out-state.png b/docs/ide/media/visualstudio/account-settings-filter-account-dialogs-tenants-filtered-out-state.png new file mode 100644 index 00000000000..b657049d81d Binary files /dev/null and b/docs/ide/media/visualstudio/account-settings-filter-account-dialogs-tenants-filtered-out-state.png differ diff --git a/docs/ide/media/visualstudio/add-personalization-account.png b/docs/ide/media/visualstudio/add-personalization-account.png new file mode 100644 index 00000000000..23cd12d5628 Binary files /dev/null and b/docs/ide/media/visualstudio/add-personalization-account.png differ diff --git a/docs/ide/media/visualstudio/apply-filter.png b/docs/ide/media/visualstudio/apply-filter.png new file mode 100644 index 00000000000..bc76a7f6331 Binary files /dev/null and b/docs/ide/media/visualstudio/apply-filter.png differ diff --git a/docs/ide/media/visualstudio/reauthenticate-account.png b/docs/ide/media/visualstudio/reauthenticate-account.png new file mode 100644 index 00000000000..878d26c8d5a Binary files /dev/null and b/docs/ide/media/visualstudio/reauthenticate-account.png differ diff --git a/docs/ide/media/visualstudio/select-system-web-browser.png b/docs/ide/media/visualstudio/select-system-web-browser.png new file mode 100644 index 00000000000..ee2c7b6520d Binary files /dev/null and b/docs/ide/media/visualstudio/select-system-web-browser.png differ diff --git a/docs/ide/media/visualstudio/windows-authentication-broker.png b/docs/ide/media/visualstudio/windows-authentication-broker.png new file mode 100644 index 00000000000..d7ee0a2c249 Binary files /dev/null and b/docs/ide/media/visualstudio/windows-authentication-broker.png differ diff --git a/docs/ide/visual-studio-github-copilot-get-started.md b/docs/ide/visual-studio-github-copilot-get-started.md index 8cb0181efeb..1c17ed1f546 100644 --- a/docs/ide/visual-studio-github-copilot-get-started.md +++ b/docs/ide/visual-studio-github-copilot-get-started.md @@ -1,7 +1,7 @@ --- title: Get Started with GitHub Copilot description: Learn how to get started with GitHub Copilot in Visual Studio. -ms.date: 2/18/2026 +ms.date: 05/11/2026 ms.update-cycle: 180-days ms.topic: get-started author: RoseHJM @@ -56,10 +56,12 @@ Copilot is now ready to use in Visual Studio. After you sign in, use Copilot in the chat window and throughout the IDE. - **Use [agent mode](copilot-agent-mode.md) and [MCP servers](mcp-servers.md)**: In the chat window, select **Ask** and switch to **Agent** to enable agent mode. Use the tools icon to access Model Context Protocol (MCP) servers, configure servers, and choose which tools Copilot can use. For example, to get Copilot assistance with generating targeted code, send "Write unit tests for the methods in this file." + - As part of agent mode workflows, Copilot Chat can connect to cloud agents to run remote coding sessions that create repository issues and pull requests in your connected GitHub repository. You might be prompted to grant repository permissions the first time you start a cloud session, or when more permissions are required. -- **Use [completions](visual-studio-github-copilot-extension.md) and [next edit suggestions](copilot-next-edit-suggestions.md)**: As you code, Copilot provides suggestions directly in the editor. Copilot suggests both new code (shown as gray text) and edits to existing code. +- **Use [completions](visual-studio-github-copilot-extension.md) and [next edit suggestions](copilot-next-edit-suggestions.md)**: As you code, Copilot provides suggestions directly in the editor. Copilot suggests both new code (shown as gray text) and edits to existing code. By default, Visual Studio prioritizes IntelliSense over Copilot inline completions. You can customize keyboard shortcuts for accepting Copilot suggestions (full suggestion, next word, and next line) in **Tools** > **Options** > **Environment** > **Keyboard**. - **Use Copilot actions across Visual Studio**: Find Copilot-powered actions and suggestions on the editor context menu, error list, feature search, and other areas of the IDE. + - Use the Debugger Agent workflow from Copilot Chat or issue context. Start from a GitHub or Azure DevOps issue (or a natural-language prompt) to reproduce a problem, generate hypotheses, add instrumentation, analyze telemetry, and apply targeted fixes while validating live runtime behavior. ## Tailor Copilot chat to your workflow @@ -71,6 +73,8 @@ Customize Copilot for your project and your development workflow. - **Add custom instructions**: Add reusable [custom instructions](copilot-chat-context.md#use-custom-instructions) in `.github/copilot-instructions.md` and [prompt files](copilot-chat-context.md#use-prompt-files) in `.github/prompts` to customize Copilot responses for your coding style or project needs. +- **Create and manage custom agents**: In the Copilot Chat window, use the agent picker at the top of the prompt area to create and select custom agents. User-level custom agent definitions are stored in `%USERPROFILE%\.github\agents`. These agents retain workspace awareness, tool configuration, model selection, and MCP connections. For more information, see [Use built-in and custom agents with GitHub Copilot](copilot-specialized-agents.md). + ## Helpful resources To review Copilot features at any time, select **GitHub Copilot Walkthrough** from the **GitHub Copilot** badge in the upper-right corner of Visual Studio. @@ -81,4 +85,4 @@ Try building a complete app with the [Hands-on lab: GitHub Copilot in Visual Stu - [GitHub Copilot Trust Center: Learn about security, privacy, compliance, and transparency](https://copilot.github.trust.page) - [Completions](visual-studio-github-copilot-extension.md) -- [Chat](visual-studio-github-copilot-chat.md) \ No newline at end of file +- [Chat](visual-studio-github-copilot-chat.md) diff --git a/docs/ide/work-with-multi-factor-authentication.md b/docs/ide/work-with-multi-factor-authentication.md index 41658a08d21..7f084f426b4 100644 --- a/docs/ide/work-with-multi-factor-authentication.md +++ b/docs/ide/work-with-multi-factor-authentication.md @@ -1,12 +1,11 @@ --- title: Multifactor authentication with Visual Studio sign-ins titleSuffix: "" -ms.date: 08/13/2024 +ms.date: 5/12/2026 ms.topic: how-to description: Use Visual Studio with accounts that require multifactor authentication (MFA) to protect your apps and data with conditional access policies. author: ghogen ms.author: ghogen - ms.subservice: general-ide ms.custom: sfi-image-nochange --- @@ -19,32 +18,31 @@ In this article, you learn to use Visual Studio with accounts that require multi When collaborating with external guest users, it's a good idea to protect your apps and data with **conditional access (CA)** policies such as **multifactor authentication (MFA)**. -Once enabled, guest users will need more than just a username and password to access your resources, and must satisfy additional security requirements. MFA policies can be enforced at the tenant, app, or individual guest user level, the same way that they're enabled for members of your own organization. +Once enabled, guest users need more than just a username and password to access your resources, and must satisfy additional security requirements. MFA policies can be enforced at the tenant, app, or individual guest user level, the same way that they're enabled for members of your own organization. > [!NOTE] > Versions of Visual Studio prior to 16.6 may have degraded authentication experiences when used with accounts that have enabled CA policies such as MFA, and are associated with two or more tenants. > -> These issues can cause your instance of Visual Studio to prompt reauthentication multiple times per day. You may have to re-enter your credentials for previously authenticated tenants, even during the course of the same Visual Studio session. +> These issues can cause your instance of Visual Studio to prompt reauthentication multiple times per day. You may have to reenter your credentials for previously authenticated tenants, even during the same Visual Studio session. ## Using Visual Studio with MFA policies - -::: moniker range="=vs-2022" - With [Visual Studio 2022 version 17.11](/visualstudio/releases/2022/release-notes), Windows authentication broker is now the default workflow for adding and reauthenticating accounts in Visual Studio. Windows authentication broker uses [Web Account Manager (WAM)](/entra/msal/dotnet/acquiring-tokens/desktop-mobile/wam) and offers many benefits such as security, improved MFA support, and seamless integration between accounts added to the OS and Visual Studio. Using WAM as the authentication mechanism in Visual Studio makes it easier to access resources secured via CA policies such as MFA. +:::moniker range="visualstudio" +:::image type="content" source="media/visualstudio/windows-authentication-broker.png" alt-text="Select web authentication broker from the dropdown."::: +:::moniker-end +:::moniker range="vs-2022" :::image type="content" source="media/vs-2022/windows-authentication-broker.png" alt-text="Select web authentication broker from the dropdown."::: +:::moniker-end If run into any [issues with using WAM](#web-account-manager-wam-errors), we recommend you [use System web browser](#enabling-system-web-browser) as the alternative to add and reauthenticate Visual Studio accounts. -::: moniker-end - > [!WARNING] > Not using this workflow could trigger a degraded experience resulting in multiple additional authentication prompts when adding or reauthenticating Visual Studio accounts. -::: moniker range="=vs-2022" ### Using Windows authentication broker @@ -59,22 +57,24 @@ You can manage your accounts from the **Account Settings** dialog in Visual Stud Using Windows Account Manager (WAM) as the authentication mechanism in Visual Studio is the recommended workflow for adding and reauthenticating accounts. However, if run into any [issues with using WAM](#web-account-manager-wam-errors), you can switch to using the system web browser. -::: moniker-end ### Enabling system web browser > [!NOTE] -> For the best experience, we recommend that you clear your system’s default web browser data before proceeding with this workflow. Additionally, if you have Work or School accounts in your Windows 10 Settings under **Access work or school**, please verify that they are properly authenticated. +> For the best experience, we recommend that you clear your system’s default web browser data before proceeding with this workflow. Additionally, if you have Work or School accounts in your Windows 10 Settings under **Access work or school**, verify that they're properly authenticated. To enable the **system web browser** workflow, go to Visual Studio's Options dialog **(Tools > Options…)**, select the **Accounts** tab and select **System web browser** from the **Add and reauthenticate accounts using:** dropdown. +:::moniker range="visualstudio" +:::image type="content" source="media/visualstudio/select-system-web-browser.png" alt-text="Select system web browser from the menu."::: +:::moniker-end + +:::moniker range="vs-2022" :::image type="content" source="media/vs-2022/select-system-web-browser.png" alt-text="Select system web browser from the menu."::: +:::moniker-end ### Sign into additional accounts with MFA policies - -::: moniker range="=vs-2022" - You can sign in or add accounts to Visual Studio via the [Profile Card](signing-in-to-visual-studio.md#add-and-switch-user-accounts-in-visual-studio) or the Account Settings dialog **(File > Account Settings…)**. **Windows authentication broker** @@ -87,29 +87,39 @@ Once the Windows authentication broker workflow is enabled, you can sign in or a Once the system web browser workflow is enabled, you can sign in or add accounts to Visual Studio as you normally would. -::: moniker-end +:::moniker range="visualstudio" +:::image type="content" source="media/visualstudio/add-personalization-account.png" alt-text="Add a new personalization account to Visual Studio." border="false"::: +:::moniker-end +:::moniker range="vs-2022" :::image type="content" source="media/vs-2022/add-personalization-account.png" alt-text="Add a new personalization account to Visual Studio." border="false"::: +:::moniker-end -This action will open your system's default web browser, ask you to sign into your account, and validate any required MFA policy. +This action opens your system's default web browser, ask you to sign into your account, and validate any required MFA policy. -During the sign-in process, you may receive an additional prompt asking you to stay signed in. This prompt will likely show up the second time an account is used to sign in. To minimize the need to re-enter your credentials, we recommend that you select **Yes**, as this ensures your credentials are preserved across browser sessions. +During the sign-in process, you may receive an additional prompt asking you to stay signed in. This prompt will likely show up the second time an account is used to sign in. To minimize the need to reenter your credentials, we recommend that you select **Yes**, as this ensures your credentials are preserved across browser sessions. :::image type="content" source="media/vs-2022/keep-me-signed-in.png" alt-text="Stay signed in?"::: -Based on your development activities and resource configuration, you may still be prompted to re-enter your credentials during your session. This can occur when you add a new resource, or try accessing a resource without having previously met its CA/MFA authorization requirements. +Based on your development activities and resource configuration, you may still be prompted to reenter your credentials during your session. This prompt can occur when you add a new resource, or try accessing a resource without having previously met its CA/MFA authorization requirements. ## Reauthenticating an account -If there's a problem with your account, Visual Studio might ask you to re-enter your account credentials. +If there's a problem with your account, Visual Studio might ask you to reenter your account credentials. + +:::moniker range="visualstudio" +:::image type="content" source="media/visualstudio/reauthenticate-account.png" alt-text="Screenshot showing account that needs reauthentication."::: +:::moniker-end +:::moniker range="vs-2022" :::image type="content" source="media/vs-2022/reauthenticate-account.png" alt-text="Screenshot showing account that needs reauthentication."::: +:::moniker-end -Clicking on **Re-enter your credentials** will open your system's default web browser and attempt to automatically refresh your credentials. If unsuccessful, you'll be asked to sign into your account and validate any required CA/MFA policy. +Clicking on **Re-enter your credentials** opens your system's default web browser and attempt to automatically refresh your credentials. If unsuccessful, you are asked to sign into your account and validate any required CA/MFA policy. -If your account is associated with multiple Azure Active Directories and runs into an access problem with one or more of them, the **Re-enter your credentials** dialog will show you the impacted directories and the associated [AADSTS error codes](/azure/active-directory/develop/reference-error-codes#aadsts-error-codes). +If your account is associated with multiple Azure Active Directories and runs into an access problem with one or more of them, the **Re-enter your credentials** dialog shows you the impacted directories and the associated [AADSTS error codes](/azure/active-directory/develop/reference-error-codes#aadsts-error-codes). -You'll be able de-select any directories that you don't want to reauthenticate and **continue** a regular signing in operation with the home directory, as well as any guest tenants that remain selected. Deselected directories won't be accessible for future use until the [account filter](work-with-multi-factor-authentication.md#how-to-filter-out-individual-tenants) is removed. +You can deselect any directories that you don't want to reauthenticate and **continue** a regular signing in operation with the home directory, and any guest tenants that remain selected. Deselected directories won't be accessible for future use until the [account filter](work-with-multi-factor-authentication.md#how-to-filter-out-individual-tenants) is removed. :::image type="content" source="media/vs-2022/reauthenticate-client-access-problem-directories.png" alt-text="Reauthenticate your Visual Studio account."::: @@ -127,11 +137,11 @@ If you're experiencing CA/MFA issues and/or are unable to log in even when using 1. Sign in again. > [!NOTE] -> After these steps you'll likely be able to log in, but your account will be put in a filtered state. While in a filtered state, only your account's default tenant and resources will be available. All other Microsoft Entra tenants and resources will become inaccessible, but you can [manually add them back](#how-to-opt-out-of-using-a-specific-microsoft-entra-tenant-in-visual-studio). +> After these steps you likely can log in, but your account is put in a filtered state. While in a filtered state, only your account's default tenant and resources are available. All other Microsoft Entra tenants and resources become inaccessible, but you can [manually add them back](#how-to-opt-out-of-using-a-specific-microsoft-entra-tenant-in-visual-studio). -### Pre-authorization issues +### Preauthorization issues -:::image type="content" source="media/vs-2022/pre-auth-general.png" alt-text="Screenshot of a pre-authorization error dialog." border="false"::: +:::image type="content" source="media/vs-2022/pre-auth-general.png" alt-text="Screenshot of a preauthorization error dialog." border="false"::: Starting with Visual Studio 2022 version 17.5, if you see the previous error dialog, try the following steps to resolve the issue: @@ -140,9 +150,8 @@ Starting with Visual Studio 2022 version 17.5, if you see the previous error dia 1. Create a new [Report a Problem](https://developercommunity.visualstudio.com/VisualStudio/report) ticket explaining the activity you were doing and/or resource you were trying to access before encountering the problem. > [!NOTE] -> Creating a ticket will help us identify problematic areas and provide the needed logs to investigate and address the issue. +> Creating a ticket helps us identify problematic areas and provide the needed logs to investigate and address the issue. -::: moniker range="=vs-2022" ### Web Account Manager (WAM) errors If you run into errors when using the [Windows authentication broker workflow for signing in to Visual Studio](#using-windows-authentication-broker), follow the action listed on the error dialog to resolve or report the issue. Use the links on the dialog to learn more about the error or to see error logs. @@ -154,13 +163,11 @@ For example, if you see the following error dialog, you can attempt to resolve t :::image type="content" source="media/vs-2022/work-with-multi-factor-authentication/change-authentication-mechanism-error.png" alt-text="Screenshot of a WAM error dialog with the change authentication mechanism option to resolve the error." border="false"::: If you need to switch to an authentication mechanism other than the Windows Broker, you can switch by following the instructions to [enable system web browser](#enabling-system-web-browser). -If those instructions don't work and you have a support contract please open a support ticket at [Technical support](https://support.serviceshub.microsoft.com/supportforbusiness/create?sapId=4fd4947b-15ea-ce01-080f-97f2ca3c76e8) - -::: moniker-end +If those instructions don't work and you have a support contract, open a support ticket at [Technical support](https://support.serviceshub.microsoft.com/supportforbusiness/create?sapId=4fd4947b-15ea-ce01-080f-97f2ca3c76e8) ## How to opt out of using a specific Microsoft Entra tenant in Visual Studio -Visual Studio 2019 version 16.6 and above offers the flexibility to filter out tenants individually or globally, effectively hiding them from Visual Studio. Filtering eliminates the need to authenticate with that tenant, but it also means that you won't be able to access any associated resources. +Visual Studio offers the flexibility to filter out tenants individually or globally, effectively hiding them from Visual Studio. Filtering eliminates the need to authenticate with that tenant, but it also means that you won't be able to access any associated resources. This functionality is useful when you have multiple tenants, but want to optimize your development environment by targeting a specific subset. It can also help in instances when you can't validate a particular CA/MFA policy, as you can filter out the offending tenant. @@ -174,30 +181,41 @@ To filter tenants that are associated with your Visual Studio account, open the

+:::moniker range="visualstudio" +:::image type="content" source="media/visualstudio/apply-filter.png" alt-text="Apply filter." border="false"::: +:::moniker-end +:::moniker range="vs-2022" :::image type="content" source="media/vs-2022/apply-filter.png" alt-text="Apply filter." border="false"::: +:::moniker-end -The **Filter account** dialog will appear, allowing you to select which tenants you want to use with your account. +The **Filter account** dialog appears, allowing you to select which tenants you want to use with your account. :::image type="content" source="media/vs-2022/select-filter-account.png" alt-text="Select account to filter."::: -After you deselect the tenant to filter, the **Account Settings** and the **Filter account** dialogs will show filtered state. +After you deselect the tenant to filter, the **Account Settings** and the **Filter account** dialogs shows filtered state. + +:::moniker range="visualstudio" +:::image type="content" source="media/visualstudio/account-settings-filter-account-dialogs-tenants-filtered-out-state.png" alt-text="Screenshot showing the filtered tenant state on the Account Settings and the Filter Account dialogs"::: +:::moniker-end +:::moniker range="vs-2022" :::image type="content" source="media/vs-2022/account-settings-filter-account-dialogs-tenants-filtered-out-state.png" alt-text="Screenshot showing the filtered tenant state on the Account Settings and the Filter Account dialogs"::: +:::moniker-end ### Networking errors with Visual Studio -During sign in, Visual Studio may experience errors related to the network which aren't usually Visual Studio product issues and may need to be investigated by local IT support. +During sign in, Visual Studio may experience errors related to the network that aren't usually Visual Studio product issues and may need to be investigated by local IT support. #### Error "Proxy authorization required If your machine or organization uses security measures such as a firewall or a proxy server, make sure you're following the [requirements to use Visual Studio behind a proxy or firewall](/visualstudio/install/install-and-use-visual-studio-behind-a-firewall-or-proxy-server). #### SSL errors -SSL errors may come in a variety of forms. Some examples are: +SSL errors may come in various forms. Some examples are: - "The underlying connection was closed" - "The SSL connection could not be established" - "Could not create SSL/TLS secure channel" - - "An existing connection was forcibly closed by the remote host.” (This can also be due to firewalls blocking the connection) + - "An existing connection was forcibly closed by the remote host." (This issue can also be due to firewalls blocking the connection) - "The underlying connection was closed: An unexpected error occurred on send" These errors may be caused by the following: @@ -222,24 +240,24 @@ These errors may be caused by the following: This error means when Visual Studio is trying to make a connection to an internet endpoint the machine refused the connection. Common Causes: - - If the address "127.0.0.1" is in the error message this means a connection to a local proxy server was attempted but the local proxy server wasn't running. + - If the address "127.0.0.1" is in the error message, this means a connection to a local proxy server was attempted but the local proxy server wasn't running. - VPN connection - Try disconnecting from any VPNs and try the connection again. If it works, you'll want to follow up with the VPN provider or your network administrator. This includes corporate VPN or third-party VPN services. - - DNS - The domain lookup on your machine has resolved to an address which doesn't point to the expected server. This means the connection is going to a different machine not running the expected services and refusing the connection. To debug this issue, you can use tools such as [NsLookup](/windows-server/administration/windows-commands/nslookup) and compare it to the [Azure IP Ranges and Service Tags](https://www.microsoft.com/en-gb/download/details.aspx?id=56519&msockid=29cb101f084a69eb165004b009d668ef). + - DNS - The domain lookup on your machine has resolved to an address that doesn't point to the expected server. This means the connection is going to a different machine not running the expected services and refusing the connection. To debug this issue, you can use tools such as [NsLookup](/windows-server/administration/windows-commands/nslookup) and compare it to the [Azure IP Ranges and Service Tags](https://www.microsoft.com/en-gb/download/details.aspx?id=56519&msockid=29cb101f084a69eb165004b009d668ef). - IPV6 - Some computers have IPV6 enabled but the network doesn't support the protocol. In this case you may see a connection refused message because the server couldn't be found. Try disabling IPV6 on the machine to see if the connection works. - SSL problems - See [SSL errors](#ssl-errors). - - Proxy or firewalls on the network - If there is a proxy or firewall on the network, it will be the first device the connection attempts to communicate with, and it may be the one refusing the connection. You can determine if the firewall or proxy server is blocking connections by asking your network administrator. Alternatively, looking at network traces can indicate which machine the connection is being made to and identify who's refusing it. If it's an internal network address, it means the proxy or firewall blocked the connection. If it's an external IP address, this usually means DNS, IPV6, or SSL problems. + - Proxy or firewalls on the network - If there's a proxy or firewall on the network, it's the first device the connection attempts to communicate with, and it may be the one refusing the connection. You can determine if the firewall or proxy server is blocking connections by asking your network administrator. Alternatively, looking at network traces can indicate which machine the connection is being made to and identify who's refusing it. If it's an internal network address, it means the proxy or firewall blocked the connection. If it's an external IP address, this usually means DNS, IPV6, or SSL problems. #### Support for network related issues Network related issues are normally related to the machine or network configuration rather than Visual Studio. [Developer Community](https://developercommunity.visualstudio.com/VisualStudio) may provide some support, but it's focused on features within Visual Studio rather than machine configuration. For network-specific support, the [Microsoft Support Community](https://answers.microsoft.com/en-us) or [Technical support](https://support.serviceshub.microsoft.com/supportforbusiness/create?sapId=4fd4947b-15ea-ce01-080f-97f2ca3c76e8) can be helpful. ### Errors on first launch -You may encounter errors when launching Visual Studio for the first time. The error dialog will show the issue that prevented Visual Studio from opening. +You may encounter errors when launching Visual Studio for the first time. The error dialog shows the issue that prevented Visual Studio from opening. #### Access denied You may see one of the following errors: @@ -250,9 +268,9 @@ You may see one of the following errors: If you encounter these errors, close any open instances of Visual Studio and delete the file or directory mentioned in the error message to resolve the issue. - Before deleting the file, check the security permissions on the file and consider logging a [Developer Community](https://developercommunity.visualstudio.com/VisualStudio) feedback ticket. This will help us better understand why access to these files or directories is being denied. + Before deleting the file, check the security permissions on the file and consider logging a [Developer Community](https://developercommunity.visualstudio.com/VisualStudio) feedback ticket. This helps us better understand why access to these files or directories is being denied. -In your feedback ticket, please include the following information to help us investigate the issue: +In your feedback ticket, include the following information to help us investigate the issue: 1. A description or screenshot of the groups and users with permissions for the file or directory mentioned in the error. To view this, right-click the file or directory, then select **Properties** > **Security**. 1. The user account you're using to run Visual Studio. 1. If the error persists when launching Visual Studio a second time. diff --git a/docs/javascript/unit-testing-javascript-with-visual-studio.md b/docs/javascript/unit-testing-javascript-with-visual-studio.md index 39204a6bbef..ae0dbcb760c 100644 --- a/docs/javascript/unit-testing-javascript-with-visual-studio.md +++ b/docs/javascript/unit-testing-javascript-with-visual-studio.md @@ -35,7 +35,6 @@ To run unit tests from the command-line, right-click the project in Solution Exp For information on setting up unit tests, see the following: - [Testing with Vitest](https://vitest.dev/guide/) -- [Testing React with Jest](https://jestjs.io/docs/tutorial-react) - [Angular testing](https://angular.io/guide/testing) - [Testing Vue.js](https://vuejs.org/guide/scaling-up/testing.html#unit-testing) @@ -104,7 +103,7 @@ The following example is based on the TypeScript React project template provided > For TypeScript, don't use the `outfile` option in *tsconfig.json*, because Test Explorer won't be able to find your unit tests. You can use the `outdir` option, but make sure that configuration files such as `package.json` and `tsconfig.json` are in the project root. > [!IMPORTANT] - > If the output from **Tests** in the Output window shows a `ReadOnlySpan` error during test discovery, use the following workaround for a known [MSBuild issue](https://github.com/dotnet/msbuild/issues/7873). For Visual Studio 2022, open the folder, *Program Files\Microsoft Visual Studio\2022\\\Common7\IDE\Extensions\TestPlatform*, and rename *System.Memory.dll* to a different name. This fix enables test discovery. + > If the output from **Tests** in the Output window shows a `ReadOnlySpan` error during test discovery, upgrade to the latest release of Visual Studio. If you still encounter the error, use the following workaround for a known [MSBuild issue](https://github.com/dotnet/msbuild/issues/7873). For Visual Studio 2022, open the folder, *Program Files\Microsoft Visual Studio\2022\\\Common7\IDE\Extensions\TestPlatform*, and rename *System.Memory.dll* to a different name. This fix enables test discovery. This workaround is not compatible with the use of code coverage. ### Run tests (.esproj) @@ -357,7 +356,7 @@ The following example is based on the ASP.NET Core Model-View-Controller project ::: moniker range="vs-2022" > [!IMPORTANT] - > If the output from **Tests** in the Output window shows a `ReadOnlySpan` error during test discovery, use the following workaround for a known [MSBuild issue](https://github.com/dotnet/msbuild/issues/7873). In Visual Studio 2022, open the folder, *Program Files\Microsoft Visual Studio\2022\\\Common7\IDE\Extensions\TestPlatform*, and rename *System.Memory.dll* to a different name. This fix enables test discovery. + > If the output from **Tests** in the Output window shows a `ReadOnlySpan` error during test discovery, upgrade to the latest release of Visual Studio. If you still encounter the error, use the following workaround for a known [MSBuild issue](https://github.com/dotnet/msbuild/issues/7873). For Visual Studio 2022, open the folder, *Program Files\Microsoft Visual Studio\2022\\\Common7\IDE\Extensions\TestPlatform*, and rename *System.Memory.dll* to a different name. This fix enables test discovery. This workaround is not compatible with the use of code coverage. ::: moniker-end ### Run tests (ASP.NET Core) diff --git a/docs/version-control/git-browse-repository.md b/docs/version-control/git-browse-repository.md index 23370c84c56..a50c50aa5f3 100644 --- a/docs/version-control/git-browse-repository.md +++ b/docs/version-control/git-browse-repository.md @@ -1,10 +1,11 @@ --- title: "Browse repos, compare branches & commits" description: Browse any Git repository in Visual Studio by using the Git Repository window to view local and remote branches and multiple branches at the same time. -ms.date: 02/25/2026 +ms.date: 05/13/2026 ms.topic: how-to author: ghogen ms.author: ghogen +ms.custom: doc-kit-assisted, awp-ai ms.subservice: general-ide @@ -139,6 +140,16 @@ To compare any two commits in your branch, use the **Ctrl** key to select the tw > [!TIP] >Similar to **Commit Details**, you can use the **Open in New Tab** button to open the comparison on a different tab or maximize it on the screen. +:::moniker range="visualstudio" + +### Review commit scope with a changes summary + +In **Git** > **View Branch History**, open any commit and select **Open changes summary**. Visual Studio shows changed lines from multiple files in one unified view, which is useful for a fast pass before deeper file-by-file review. + +:::image type="content" source="media/visualstudio/multi-file-summary-diff-git-changes-button.png" alt-text="Screenshot showing Open changes summary in commit details." ::: + +:::moniker-end + ## Create a branch from a commit In Visual Studio, you can use the **Git Graph** pane in the **Git Repository** window to create branches from previous commits. To do so, right-click the commit you would like to create a new branch from, and then select **[New Branch](git-create-branch.md)**. diff --git a/docs/version-control/git-create-pull-request.md b/docs/version-control/git-create-pull-request.md index 8ed130594b7..ff8ac836555 100644 --- a/docs/version-control/git-create-pull-request.md +++ b/docs/version-control/git-create-pull-request.md @@ -2,11 +2,12 @@ title: Create a pull request in Visual Studio titleSuffix: "" description: Create a pull request in Visual Studio by using GitHub or Azure DevOps. -ms.date: 03/23/2026 +ms.date: 05/13/2026 ms.update-cycle: 180-days ms.topic: how-to author: ghogen ms.author: ghogen +ms.custom: doc-kit-assisted, awp-ai ms.collection: ce-skilling-ai-copilot ms.subservice: general-ide @@ -77,10 +78,17 @@ To create a pull request, follow these steps: 1. The difference preview allows you to see all the changes in the files that have been committed as a part of your pull request. See [Compare files - diff view](../ide/compare-with.md). > [!TIP] - > The summary difference view option allows you to review only the changed sections of code. + > Select **Open changes summary** to open a multi-line summary diff, which shows changed lines from multiple files in one unified view for faster review. + + > [!NOTE] + > The pull requests list entry point in **View** > **Git Repository** is currently available in Visual Studio Insiders with the preview feature **View pull requests for a Git repository**. :::image type="content" source="media/vs-2022/git-create-pr-summary-diff.png" alt-text="The New Pull Request window with the summary button text highlighted in Visual Studio 2022."::: + If you're using the pull requests list preview entry point, the **Open changes summary** button appears in that list. + + + 1. You can link work items by referencing them with the [issue search](https://devblogs.microsoft.com/visualstudio/reference-github-issues-and-pull-requests-in-visual-studio/), by typing `#` in the description box or pressing the **#** button in the lower right corner. You can also add your reviewers by typing their GitHub username or Azure DevOps identity or email. :::image type="content" source="media/vs-2022/git-create-pr-issue-search.png" alt-text="The New Pull Request with # in the description box and a list of the related GitHub issues and pull requests shown in Visual Studio 2022."::: diff --git a/docs/version-control/git-make-commit.md b/docs/version-control/git-make-commit.md index 0c3ffe3be46..158c2856098 100644 --- a/docs/version-control/git-make-commit.md +++ b/docs/version-control/git-make-commit.md @@ -2,8 +2,8 @@ title: Make a Git commit in Visual Studio titleSuffix: "" description: Make a Git commit in Visual Studio by using Git providers such as GitHub or Azure DevOps, or locally with no provider at all. -ms.date: 03/12/2026 -ms.custom: awp-ai +ms.date: 05/13/2026 +ms.custom: awp-ai, doc-kit-assisted ms.update-cycle: 180-days ms.topic: how-to author: ghogen @@ -60,6 +60,20 @@ You can also choose not to stage your modified files by skipping the staging are Visual Studio also makes it easy to commit and sync with one click by using the **Commit All and Push** and **Commit All and Sync** shortcuts. When you double-click any file in the **Changes** and the **Staged changes** sections, you can see a line-by-line comparison with the unmodified version of the file. See [Compare files - diff view](../ide/compare-with.md). +:::moniker range="visualstudio" + +### Review changed lines across files + +To quickly understand the scope of your pending commit, select **Open changes summary** in the **Git Changes** window. Visual Studio shows changed lines from multiple files in one unified view, so you can triage changes before you commit. + +:::image type="content" source="media/visualstudio/multi-file-summary-diff-git-changes-button.png" alt-text="Screenshot showing Open changes summary in the Git Changes toolbar." ::: + +After you open the summary, Visual Studio displays changed lines from multiple files in one view. + +:::image type="content" source="media/visualstudio/multi-file-summary-diff-collapsed-2.png" alt-text="Screenshot showing changed lines from multiple files in a unified summary view." ::: + +:::moniker-end + :::moniker range="<=vs-2022" :::image type="content" source="media/vs-2022/git-file-version-compare.png" alt-text="The line-by-line comparison of file versions in Visual Studio 2022." lightbox="media/vs-2022/git-file-version-compare.png"::: @@ -74,13 +88,13 @@ Visual Studio also makes it easy to commit and sync with one click by using the :::moniker range=">=vs-2022" -New in [**version 17.6**](/visualstudio/releases/2022/release-notes-v17.6): You can also reference an issue or a pull request by typing `#` or selecting the **#** button in the lower right side of the commit message text box. For more information, see the [Reference issues and pull requests](https://devblogs.microsoft.com/visualstudio/reference-github-issues-and-pull-requests-in-visual-studio/) blog post. +You can also reference an issue or a pull request by typing `#` or selecting the **#** button in the lower right side of the commit message text box. For more information, see the [Reference issues and pull requests](https://devblogs.microsoft.com/visualstudio/reference-github-issues-and-pull-requests-in-visual-studio/) blog post. -New in [**version 17.12**](/visualstudio/releases/2022/release-notes-v17.12): When you rename a file, you'll see a notification bar at the top of the **Git Changes** window informing you that a file was renamed, and prompting you to stage that change. This notification appears before you stage or commit anything. You might want to stage and commit the change before making other changes, in order to ensure that Git detects the change as a rename, not a deletion and addition of a new file. +When you rename a file, you'll see a notification bar at the top of the **Git Changes** window informing you that a file was renamed, and prompting you to stage that change. This notification appears before you stage or commit anything. You might want to stage and commit the change before making other changes, in order to ensure that Git detects the change as a rename, not a deletion and addition of a new file. ### Review local changes with Copilot Chat -New in **version 17.13**: With [GitHub Copilot](../ide/visual-studio-github-copilot-install-and-states.md) installed, you can have GitHub Copilot review your code changes before you commit them. +With [GitHub Copilot](../ide/visual-studio-github-copilot-install-and-states.md) installed, you can have GitHub Copilot review your code changes before you commit them. :::moniker-end @@ -170,7 +184,7 @@ When you double-click a **Commit**, Visual Studio opens its details in a separat ## Generate commit messages with GitHub Copilot Chat -With Visual Studio version 17.9 and later and the GitHub Copilot extensions, you can use AI to generate detailed commit messages that describe your changes. +With Visual Studio and the GitHub Copilot, you can use AI to generate detailed commit messages that describe your changes. > [!NOTE] > To enable AI-generated commit messages, you need GitHub Copilot and GitHub Copilot Chat. To get started, see [Manage GitHub Copilot installation and state](../ide/visual-studio-github-copilot-install-and-states.md). @@ -198,14 +212,20 @@ When you're ready to make a commit, use the sparkly pen icon (tooltip: **Add AI :::moniker range="visualstudio" -You can customize the commit message format globally by giving additional guidance in the prompt for GitHub Copilot. To add custom prompt instructions, open the **Tools** > **Options** pane, and expand the **All Settings** > **GitHub** > **Copilot** > **Source Control Integration** section. In the **Commit message custom instructions** box, enter your additions to the prompt text. The changes affect every commit message. With this prompt guidance in place, teams can standardize commit message formats. +If you've been using the **Commit message custom instructions** text box under **GitHub** > **Copilot** > **Source Control Integration** to tailor Copilot-generated commit messages, that setting no longer applies. + +Going forward, manage commit message instructions in your repository's Copilot instructions file. This setup keeps commit message guidance in the same place as your other Copilot custom instructions. + +### Set up custom instructions + +Add your commit message instructions to your repository's Copilot instructions file. For setup steps, see [Add repository instructions](https://docs.github.com/en/copilot/how-tos/configure-custom-instructions/add-repository-instructions?tool=visualstudio). -:::image type="content" source="./media/visualstudio/git-customize-commit-message-with-ai.png" border="false" alt-text="Screenshot that shows how to to add a custom prompt for commit message with Tools Options." lightbox="./media/visualstudio/git-customize-commit-message-with-ai.png"::: + :::image type="content" source="./media/visualstudio/commit-message-custom-instructions.png" alt-text="Screenshot showing a Copilot instructions file with commit message rules." lightbox="./media/visualstudio/commit-message-custom-instructions.png"::: :::moniker-end :::moniker range="<=vs-2022" -With Visual Studio 2022 version 17.12 and later, you can customize the commit message format globally by giving additional guidance in the prompt for GitHub Copilot. +With Visual Studio 2022, you can customize the commit message format globally by giving additional guidance in the prompt for GitHub Copilot. To add custom prompt instructions, open the **Tools** > **Options** dialog, and expand the **GitHub** > **Copilot** section. Under **Source Control Integration** group, enter your additions to the prompt text in the **Commit message custom instructions** box and select **OK**. The changes affect every commit message. With this prompt guidance in place, teams can standardize commit message formats. diff --git a/docs/version-control/media/visualstudio/commit-message-custom-instructions.png b/docs/version-control/media/visualstudio/commit-message-custom-instructions.png new file mode 100644 index 00000000000..f6fe07bb670 Binary files /dev/null and b/docs/version-control/media/visualstudio/commit-message-custom-instructions.png differ diff --git a/docs/version-control/media/visualstudio/git-agent-code-review-comment-2.png b/docs/version-control/media/visualstudio/git-agent-code-review-comment-2.png new file mode 100644 index 00000000000..ffc33d76af7 Binary files /dev/null and b/docs/version-control/media/visualstudio/git-agent-code-review-comment-2.png differ diff --git a/docs/version-control/media/visualstudio/multi-file-summary-diff-collapsed-2.png b/docs/version-control/media/visualstudio/multi-file-summary-diff-collapsed-2.png new file mode 100644 index 00000000000..d7c22a2b064 Binary files /dev/null and b/docs/version-control/media/visualstudio/multi-file-summary-diff-collapsed-2.png differ diff --git a/docs/version-control/media/visualstudio/multi-file-summary-diff-collapsed.png b/docs/version-control/media/visualstudio/multi-file-summary-diff-collapsed.png new file mode 100644 index 00000000000..31f3b2939d6 Binary files /dev/null and b/docs/version-control/media/visualstudio/multi-file-summary-diff-collapsed.png differ diff --git a/docs/version-control/media/visualstudio/multi-file-summary-diff-git-changes-button.png b/docs/version-control/media/visualstudio/multi-file-summary-diff-git-changes-button.png new file mode 100644 index 00000000000..4003e4e3aa9 Binary files /dev/null and b/docs/version-control/media/visualstudio/multi-file-summary-diff-git-changes-button.png differ