Skip to content

Repo sync for protected branch #10724

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 7 commits into from
Apr 22, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions docs/debugger/how-to-use-the-disassembly-window.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
title: View Disassembly Code in the debugger
description: Use the Disassembly window in Visual Studio to show assembly code corresponding to the instructions created by the compiler.
ms.date: 08/15/2023
ms.date: 04/18/2025
ms.topic: how-to
f1_keywords:
- vs.debug.disassembly
Expand Down Expand Up @@ -32,7 +32,7 @@ This feature is only available if address-level debugging is enabled. It isn't a

In addition to assembly instructions, the **Disassembly** window can show the following optional information:

- Memory address where each instruction is located. For native applications, it is the actual memory address. For Visual Basic or C#, it's an offset from the beginning of the function.
- Memory address where each instruction is located. For native applications, it's the actual memory address. For Visual Basic or C#, it's an offset from the beginning of the function.

- Source code from which the assembly code derives.

Expand All @@ -52,10 +52,10 @@ To view machine-code instructions in their raw numeric form, rather than as asse

To enable the **Disassembly** window, under **Tools** > **Options** > **Debugging**, select **Enable address-level debugging**.

To open the **Disassembly** window during debugging, select **Windows** > **Disassembly** or press **Alt**+**8**.
To open the **Disassembly** window during debugging, select **Debug** > **Windows** > **Disassembly** or press **Ctrl** + **Alt** + **D**.

> [!NOTE]
> The dialog boxes and menu commands you see might differ from those described in Help depending on your active settings or edition. To change your settings, choose **Import and Export Settings** on the **Tools** menu. For more information, see [Reset all settings](../ide/personalizing-the-visual-studio-ide.md#reset-all-settings).
> The dialog boxes and menu commands you see might differ from those described in this article depending on your active settings or edition. To change your settings, choose **Import and Export Settings** on the **Tools** menu. For more information, see [Reset all settings](../ide/personalizing-the-visual-studio-ide.md#reset-all-settings).

To turn optional information on or off, right-click in the **Disassembly** window, and set or clear the desired options in the shortcut menu.

Expand All @@ -69,11 +69,11 @@ When you view memory contents in a **Memory** window or the **Disassembly** wind

2. To page up (move to a lower memory address), click the vertical scrollbar above the thumb.

You will also notice that the vertical scrollbar operates in a nonstandard manner. The address space of a modern computer is very large, and it would be easy to get lost by grabbing the scrollbar thumb and dragging it to a random location. For this reason, the thumb is "springloaded" and always remains in the center of the scrollbar. In native code applications, you can page up or down, but cannot scroll about freely.
You'll also notice that the vertical scrollbar operates in a nonstandard manner. The address space of a modern computer is very large, and it would be easy to get lost by grabbing the scrollbar thumb and dragging it to a random location. For this reason, the thumb is "springloaded" and always remains in the center of the scrollbar. In native code applications, you can page up or down, but can't scroll about freely.

In managed applications, disassembly is limited to one function and you can scroll normally.

You will notice that the higher addresses appear at the bottom of the window. To view a higher address, you must move down, not up.
You'll notice that the higher addresses appear at the bottom of the window. To view a higher address, you must move down, not up.

### Move up or down one instruction

Expand Down
37 changes: 29 additions & 8 deletions docs/install/update-visual-studio.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,10 +2,9 @@
title: Update Visual Studio installation to recent release
titleSuffix: ''
description: Update your Visual Studio installation to the most recent release to access the latest feature changes and fixes for known issues.
ms.date: 9/3/2024
ms.date: 4/21/2025
ms.custom: vs-acquisition
ms.topic: how-to

ms.subservice: installation
helpviewer_keywords:
- update [Visual Studio]
Expand All @@ -24,15 +23,25 @@ If you are an IT Administrator and want to configure your organization's clients

## Before you update

By default, in order to install, update, or modify Visual Studio, the account performing the update must have administrative permissions on the machine and also must have permissions to the source where the product updates are located (either the internet or an internal location). If you are logged in as a typical user and try to perform one of these commands, then you'll get a User Account Control notice prompting you for admin credentials. Starting in August 2023, an admin can delegate control of updates to standard users by configuring the [`AllowStandardUserControl` policy](https://aka.ms/vs/setup/policies). For more information, see [User Permissions and Visual Studio](../ide/user-permissions-and-visual-studio.md).
By default, to install, update, or modify Visual Studio, the account performing the update needs administrative permissions on the machine and access to the update source (either the internet or an internal location). If you're using a standard account, you'll get a User Account Control prompt for admin credentials.

Since August 2023, an admin can let standard users run updates by configuring the [`AllowStandardUserControl` policy](https://aka.ms/vs/setup/policies). For details, see [User Permissions and Visual Studio](../ide/user-permissions-and-visual-studio.md).

Visual Studio must be closed before performing an update. We highly recommend saving your work before performing an update.
Make sure to close Visual Studio and save your work before updating.

::: moniker range="vs-2019"

We encourage you to update to the most [recent release](/visualstudio/releases/2019/release-notes/) of Visual Studio 2019 so that you always get the latest features, security fixes, and improvements. And if you'd like to try out our newest version, consider downloading and installing [Visual Studio 2022](https://visualstudio.microsoft.com/downloads/?cid=learn-onpage-download-cta).

There are several different ways to update an installation of Visual Studio. You can update through the Visual Studio Installer, you can check for updates or use the Notification hub in the IDE, you can configure Visual Studio to update on close, you can update by running a [specific version of the bootstrapper](/visualstudio/releases/2019/history), you can update Visual Studio programmatically, or you can be part of an organization that uses Administrator updates. Here's how to update Visual Studio 2019 using these various methods.
There are several ways to update an installation of Visual Studio:
- By using the Visual Studio Installer
- By checking for updates or using the Notification hub in the IDE
- By configuring update on close
- By running a [specific version of the bootstrapper](/visualstudio/releases/2019/history)
- Programmatically
- Or by being part of an organization that uses Administrator updates.

Here's how to update Visual Studio 2019 using these various methods.

## Use the Visual Studio Installer

Expand Down Expand Up @@ -92,6 +101,7 @@ Visual Studio setup features and bug fixes are typically implemented in the inst
![Screenshot showing the 'Check for Updates' from the Help menu.](media/vs-2019/vs-ide-check-updates-help-menu.png "Choose 'Check for Updates' from the Help menu")

## Run a specific bootstrapper to update the product to a specific version

If you're an Enterprise or Professional customer, you can update your instance of Visual Studio 2019 to any specific version that has been released, as long as it's a higher version than what is currently installed. To update your instance of Visual Studio 2019 via this method, [navigate to the Visual Studio 2019 release history page](/visualstudio/releases/2019/history), download the bootstrapper that corresponds to the desired update version into your product installation directory, and then double click on it to initiate the update.

## Customize update settings
Expand All @@ -109,6 +119,7 @@ There are several different settings that can be customized to control the updat
1. Observe the configuration options that are available to set in this dialog. You can choose the **Automatically download updates** setting, which allows updates to download while your machine is idle. There are also two installation modes to choose from: **Install while downloading**, and **Download all, then install**. Choose the installation mode and the automatic download setting you want for your Visual Studio updates.

### Configure source location of updates

If you're in an enterprise environment, then it's possible to configure the location that your client instances look for updates. This is useful in situations where your client installed from a network layout, but you later want the clients to get updates from a different network layout. The ability to configure update locations requires the presence of the newer Visual Studio 2022 installer, which can be obtained by [acquiring the latest installer on the client machine](#use-the-latest-and-greatest-installer), or by an administrator [pushing the latest installer out through a network layout](create-a-network-installation-of-visual-studio.md#ensure-your-layout-is-using-the-latest-installer). For more information about how to use this feature, refer to the [Visual Studio 2022 documentation on configuring source location of updates](/visualstudio/install/update-visual-studio?view=vs-2022&preserve-view=true#configure-source-location-of-updates-1).

::: moniker-end
Expand All @@ -117,7 +128,15 @@ If you're in an enterprise environment, then it's possible to configure the loca

We encourage you to update to the most [recent release](/visualstudio/releases/2022/release-notes) of Visual Studio 2022 so that you always get the latest features, security fixes, and improvements.

There are many different ways to update an installation of Visual Studio. You can update through the Visual Studio Installer, you can check for updates or use the notification hub in the IDE, you configure Visual Studio to update upon close, you can update by running a [specific version of the bootstrapper](/visualstudio/releases/2022/release-history), you can update Visual Studio programmatically, or you can be part of an organization that uses Administrator updates. Here's how to update Visual Studio 2022 using these various methods.
There are several ways to update an installation of Visual Studio:
- By using the Visual Studio Installer
- By checking for updates or using the Notification hub in the IDE
- By configuring update on close
- By running a [specific version of the bootstrapper](/visualstudio/releases/2022/release-history)
- Programmatically
- Or by being part of an organization that uses Administrator updates.

Here's how to update Visual Studio 2022 using these various methods.

## Use the Visual Studio Installer

Expand Down Expand Up @@ -180,6 +199,7 @@ There are many different ways to update an installation of Visual Studio. You ca
![Screenshot showing the 'Check for Updates' option in the Help menu.](media/vs-2022/ide-check-updates-help-menu.png "Choose 'Check for Updates' from the Help menu")

## Run a specific bootstrapper to update the product to a specific version

If you're an Enterprise or Professional customer, you can update your instance of Visual Studio 2022 to any specific version that has been released, as long as it's a higher version than what is currently installed. To update your instance of Visual Studio 2022 via this method, [navigate to the Visual Studio 2022 release history page](/visualstudio/releases/2022/release-history), download the bootstrapper that corresponds to the desired update version into your product installation directory, and then double-click on it to initiate the update.

## Customize update settings
Expand All @@ -197,11 +217,12 @@ There are several different settings that can be customized to control the updat
- There are also two installation modes to choose from: **Install while downloading** and **Download all, then install**.

### Configure source location of updates

With Visual Studio 2022, you can now configure where your clients will get their updates from. These update source locations are called *channels*, and you can find more information about channel purpose and availability in the [Visual Studio Release Rhythm](/visualstudio/productinfo/release-rhythm) documentation. Microsoft makes both the Current and the Preview channels available to everyone, and the [long term servicing channels (LTSCs) are available to Enterprise and Professional customers for about 18 months](/visualstudio/productinfo/vs-servicing#long-term-servicing-channel-ltsc-support). IT Administrators can also configure the update source locations, such as network layouts, that the clients should have access to. Refer to the [Visual Studio Administrators Guide](https://aka.ms/vs/admin/guide) for additional approach recommendations, and to the [modifySettings command documentation](/visualstudio/install/use-command-line-parameters-to-install-visual-studio#modifysettings-command-and-command-line-parameters) for how to access this functionality programmatically.

There are two ways to bring up the Update Settings dialog, which allows you to manually change the channel that your Visual Studio instance should get its updates from.

1. Open the Visual Studio installer, select the instance you want to configure, choose the **More button** and then choose the **Update settings** menu option. Refer to previous instructions for how to find the Visual Studio Installer.
1. Open the Visual Studio Installer, select the instance you want to configure, choose the **More button** and then choose the **Update settings** menu option. Refer to previous instructions for how to find the Visual Studio Installer.

![Screenshot showing the Updates settings in the Installer.](media/vs-2022/installer-update-settings-menu-option.png)

Expand Down Expand Up @@ -254,7 +275,7 @@ You can also configure a specific Visual Studio instance to *persistently* remov

The most current release of the installer in the latest version of Visual Studio typically has the most robust and reliable feature set. This functionality will often seamlessly work on lower versioned products. In order to manually acquire the latest version of the installer onto a client machine (like if you wanted the functionality of the latest Visual Studio 2022 installer to govern a Visual Studio 2019 installation), you can do one of the following:

1. [Download any recent bootstrapper for the latest version of Visual Studio](/visualstudio/install/install-visual-studio#step-2---download-visual-studio) and then either
1. [Download any recent bootstrapper for the latest version of Visual Studio](/visualstudio/releases/2022/release-history#release-dates-and-build-numbers) and then either

- Double click on the bootstrapper to initiate the installation. The latest installer will get installed onto the machine first. Once the "Choose Workloads" screen pops up, simply cancel the installation.

Expand Down