Skip to content

Repo sync for protected CLA branch #7021

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
Sep 1, 2021
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
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
title: Customize menus and toolbars
description: Learn how to customize Visual Studio menus and toolbars, and also learn how to customize any commands included in the menus and toolbars.
ms.custom: SEO-VS-2020
ms.date: 11/04/2016
ms.date: 09/01/2021
ms.topic: how-to
f1_keywords:
- vs.renametoolbar
Expand Down Expand Up @@ -35,8 +35,8 @@ ms.workload:

You can customize Visual Studio not only by adding and removing toolbars and menus on the menu bar, but also by adding and removing commands on any given toolbar or menu.

> [!WARNING]
> After you customize a toolbar or menu, make sure that its check box remains selected in the **Customize** dialog box. Otherwise, your changes won't persist after you close and reopen Visual Studio.
> [!TIP]
> To learn more about how to personalize the toolbar so that you can make it yours, see our recent blog post, [**Optimizing toolbars for your workflow**](https://devblogs.microsoft.com/visualstudio/optimizing-toolbars-for-your-workflow/).

## Add, remove, or move a menu on the menu bar

Expand Down Expand Up @@ -80,6 +80,9 @@ You can customize Visual Studio not only by adding and removing toolbars and men

## <a name="customizing_menu">Customize a menu or a toolbar</a>

> [!WARNING]
> After you customize a toolbar or menu, make sure that its check box remains selected in the **Customize** dialog box. Otherwise, your changes won't persist after you close and reopen Visual Studio.

1. On the menu bar, choose **Tools** > **Customize**.

The **Customize** dialog box opens.
Expand Down
9 changes: 7 additions & 2 deletions docs/ide/managing-project-and-solution-properties.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
title: Manage project and solution properties
description: Learn how to manage both the project properties and the solution properties in Visual Studio.
ms.custom: SEO-VS-2020
ms.date: 11/04/2016
ms.date: 09/01/2021
ms.topic: conceptual
author: TerryGLee
ms.author: tglee
Expand All @@ -13,7 +13,12 @@ ms.workload:
---
# Manage project and solution properties

Projects have properties that govern many aspects of compilation, debugging, testing and deploying. Some properties are common among all project types, and some are unique to specific languages or platforms. You access project properties by right-clicking the project node in **Solution Explorer** and choosing **Properties** or by typing **properties** into the search box on the menu bar and choosing **Properties Window** from the results.
Projects have properties that govern many aspects of compilation, debugging, testing and deploying. Some properties are common among all project types, and some are unique to specific languages or platforms.

> [!TIP]
> In [Visual Studio 2022 Preview](/visualstudio/releases/2022/release-notes-preview), we've added new functionality to project properties and refreshed its user interface. To learn more, see the [**Revamped Project Properties UI**](https://devblogs.microsoft.com/visualstudio/flexible-theming-visual-studio/) blog post.

You access project properties by right-clicking the project node in **Solution Explorer** and choosing **Properties**, or by typing **properties** into the search box on the menu bar and choosing **Properties Window** from the results.

![Project context menu](../ide/media/vs2015_proj_prop_menu.gif)

Expand Down
6 changes: 3 additions & 3 deletions docs/test/remote-testing.md
Original file line number Diff line number Diff line change
Expand Up @@ -110,15 +110,15 @@ The environment can be specified in `testEnvironments.json` in the root of your
## Use the Test Explorer to run and debug remote tests
* The active environment is selected via a drop-down in the Test Explorer tool bar. Currently, only one test environment can be active at a time.

![Remote testing environment drop down in Test Explorer](media/remote_test_drop_down.png)
![Remote testing environment drop down in Test Explorer](media/remote-test-drop-down.png)

* Once an environment is selected, tests are discovered and run in the new environment.

![Tests are discovered and executed in remote environments](media/remote_test_linux_discovery.png)
![Tests are discovered and executed in remote environments](media/remote-test-linux-discovery.png)

* You can now run your tests inside the remote and debug your tests in environments!

![View test results from remote environment in the test explorer](media/remote_test_linux_passing.png)
![View test results from remote environment in the test explorer](media/remote-test-linux-passing.png)

* Test Explorer may prompt you to install some missing environment prerequisites and attempt to install missing dependencies. However, the bulk of the provisioning of the remote environment is up to the user’s specification.

Expand Down