Skip to content

Commit e1adff8

Browse files
committed
, to > in successive menu choices
1 parent 745f2e1 commit e1adff8

15 files changed

+67
-66
lines changed

docs/code-quality/in-source-suppression-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ In C++/CLI, use the macros CA\_SUPPRESS\_MESSAGE or CA\_GLOBAL\_SUPPRESS_MESSAGE
2929
> You should not use in-source suppressions on release builds, to prevent shipping the in-source suppression metadata accidentally. Additionally, because of the processing cost of in-source suppression, the performance of your application can be degraded.
3030
3131
> [!NOTE]
32-
> If you migrate a project to Visual Studio 2017, you might suddenly be faced with an overwhelming number of code analysis warnings. If you aren't ready to fix the warnings and want to temporarily turn code analysis off, open the project's property pages (**Project** > ***project* Properties**) and go to the **Code Analysis** tab. Deselect **Enable Code Analysis on Build**, and then rebuild your project. Alternatively, you can select a different, smaller rule set to run against the code. Remember to turn code analysis back on when you are ready to fix the warnings.
32+
> If you migrate a project to Visual Studio 2017, you might suddenly be faced with an overwhelming number of code analysis warnings. If you aren't ready to fix the warnings and want to temporarily turn code analysis off, open the project's property pages (**Project** > **\<project> Properties**) and go to the **Code Analysis** tab. Deselect **Enable Code Analysis on Build**, and then rebuild your project. Alternatively, you can select a different, smaller rule set to run against the code. Remember to turn code analysis back on when you are ready to fix the warnings.
3333
3434
## SuppressMessage attribute
3535

docs/data-tools/handle-a-concurrency-exception.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -65,7 +65,7 @@ This walkthrough uses SQL Server Express LocalDB and the Northwind sample databa
6565

6666
#### To create a new Windows Forms application project
6767

68-
1. In Visual Studio, on the **File** menu, select **New**, **Project**.
68+
1. In Visual Studio, on the **File** menu, select **New** > **Project**.
6969

7070
2. Expand either **Visual C#** or **Visual Basic** in the left-hand pane, then select **Windows Desktop**.
7171

docs/data-tools/save-data-in-a-transaction.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ This walkthrough uses SQL Server Express LocalDB and the Northwind sample databa
4545

4646
#### To create the new Windows project
4747

48-
1. In Visual Studio, on the **File** menu, select **New**, **Project**.
48+
1. In Visual Studio, on the **File** menu, select **New** > **Project**.
4949

5050
2. Expand either **Visual C#** or **Visual Basic** in the left-hand pane, then select **Windows Desktop**.
5151

docs/data-tools/save-data-to-a-database-multiple-tables.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -63,7 +63,7 @@ This walkthrough uses SQL Server Express LocalDB and the Northwind sample databa
6363

6464
#### To create the new Windows forms application project
6565

66-
1. In Visual Studio, on the **File** menu, select **New**, **Project**.
66+
1. In Visual Studio, on the **File** menu, select **New** > **Project**.
6767

6868
2. Expand either **Visual C#** or **Visual Basic** in the left-hand pane, then select **Windows Desktop**.
6969

docs/data-tools/save-data-with-the-tableadapter-dbdirect-methods.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -56,7 +56,7 @@ This walkthrough uses SQL Server Express LocalDB and the Northwind sample databa
5656

5757
#### To create the new Windows project
5858

59-
1. In Visual Studio, on the **File** menu, select **New**, **Project**.
59+
1. In Visual Studio, on the **File** menu, select **New** > **Project**.
6060

6161
2. Expand either **Visual C#** or **Visual Basic** in the left-hand pane, then select **Windows Desktop**.
6262

docs/data-tools/walkthrough-creating-a-wcf-data-service-with-wpf-and-entity-framework.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -148,7 +148,7 @@ In the next steps, you will create a Windows Forms client application to consume
148148

149149
#### To create the client application
150150

151-
1. On the menu bar, choose File, **Add**, **New Project**.
151+
1. On the menu bar, choose File, **Add** > **New Project**.
152152

153153
2. In the **New Project** dialog box, expand the **Visual Basic** or **Visual C#** node and choose the **Windows** node, and then choose **Windows Forms Application**.
154154

docs/data-tools/walkthrough-creating-an-n-tier-data-application.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -71,7 +71,7 @@ This walkthrough uses SQL Server Express LocalDB and the Northwind sample databa
7171
7272
#### To create the n-tier solution and DataEntityTier class library
7373

74-
1. In Visual Studio, on the **File** menu, select **New**, **Project**.
74+
1. In Visual Studio, on the **File** menu, select **New** > **Project**.
7575

7676
2. Expand either **Visual C#** or **Visual Basic** in the left-hand pane, then select **Windows Desktop**.
7777

@@ -88,7 +88,7 @@ This walkthrough uses SQL Server Express LocalDB and the Northwind sample databa
8888

8989
#### To create a separate class library for the TableAdapters
9090

91-
1. Right-click on the solution in Solution Explorer and choose **Add**, **New Project**.
91+
1. Right-click on the solution in Solution Explorer and choose **Add** > **New Project**.
9292

9393
2. In the **New Project** dialog box, in the middle pane, select **Class Library**.
9494

@@ -158,7 +158,7 @@ This walkthrough demonstrates how to access the data access tier by using a WCF
158158

159159
#### To create a new WCF Service application
160160

161-
1. Right-click on the solution in Solution Explorer and choose **Add**, **New Project**.
161+
1. Right-click on the solution in Solution Explorer and choose **Add** > **New Project**.
162162

163163
2. In the **New Project** dialog box, in the left-hand pane, select **WCF**. In the middle pane, select **WCF Service Library**.
164164

@@ -282,7 +282,7 @@ This walkthrough demonstrates how to access the data access tier by using a WCF
282282

283283
#### To create the presentation tier project
284284

285-
1. Right-click on the solution in Solution Explorer and choose **Add**, **New Project**.
285+
1. Right-click on the solution in Solution Explorer and choose **Add** > **New Project**.
286286

287287
2. In the **New Project** dialog box, in the left-hand pane, select **Windows Desktop**. In the middle pane, select **Windows Forms App**.
288288

docs/data-tools/walkthrough-creating-linq-to-sql-classes-by-using-single-table-inheritance-o-r-designer.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -87,7 +87,7 @@ The [LINQ to SQL Tools in Visual Studio](../data-tools/linq-to-sql-tools-in-visu
8787

8888
#### To create the new Windows Forms Application
8989

90-
1. In Visual Studio, on the **File** menu, select **New**, **Project**.
90+
1. In Visual Studio, on the **File** menu, select **New** > **Project**.
9191

9292
2. Expand either **Visual C#** or **Visual Basic** in the left-hand pane, then select **Windows Desktop**.
9393

docs/designers/image-editor.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ This section describes how to add an image to your Visual Studio project and con
4040

4141
### To add an image to your project
4242

43-
1. In **Solution Explorer**, open the shortcut menu for the project that you want to add the image to, and then choose **Add**, **New Item**.
43+
1. In **Solution Explorer**, open the shortcut menu for the project that you want to add the image to, and then choose **Add** > **New Item**.
4444

4545
2. In the **Add New Item** dialog box, under **Installed**, select **Graphics**, and then select an appropriate file format for the image. For information about how to choose a file format based on your requirements, see the following section.
4646

docs/designers/shader-designer.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ This section describes how to add a DGSL shader to your [!INCLUDE[vsprvs](../cod
3737

3838
### To add a DGSL shader to your project
3939

40-
1. In **Solution Explorer**, open the shortcut menu for the project that you want to add the shader to, and then choose **Add**, **New Item**.
40+
1. In **Solution Explorer**, open the shortcut menu for the project that you want to add the shader to, and then choose **Add** > **New Item**.
4141

4242
2. In the **Add New Item** dialog box, under **Installed**, select **Graphics**, and then select **Visual Shader Graph (.dgsl)**.
4343

docs/modeling/design-time-code-generation-by-using-t4-text-templates.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -36,11 +36,11 @@ Design-time T4 text templates let you generate program code and other files in y
3636

3737
1. Create a [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)] project, or open an existing one.
3838

39-
For example, on the **File** menu, choose **New**, **Project**.
39+
For example, on the **File** menu, choose **New** > **Project**.
4040

4141
2. Add a text template file to your project and give it a name that has the extension **.tt**.
4242

43-
To do this, in **Solution Explorer**, on the shortcut menu of your project, choose **Add**, **New Item**. In the **Add New Item** dialog box select **Text Template** from the middle pane.
43+
To do this, in **Solution Explorer**, on the shortcut menu of your project, choose **Add** > **New Item**. In the **Add New Item** dialog box select **Text Template** from the middle pane.
4444

4545
Notice that the **Custom Tool** property of the file is **TextTemplatingFileGenerator**.
4646

docs/modeling/run-time-text-generation-with-t4-text-templates.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -49,7 +49,7 @@ Using a template in your application makes it is easier to see the final form of
4949

5050
### To create a run-time text template
5151

52-
1. In Solution Explorer, on the shortcut menu of your project, choose **Add**, **New Item**.
52+
1. In Solution Explorer, on the shortcut menu of your project, choose **Add** > **New Item**.
5353

5454
2. In the **Add New Item** dialog box, select **Runtime Text Template**. (In Visual Basic look under **Common Items** > **General**.)
5555

docs/test/live-unit-testing-start.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -5,12 +5,12 @@ ms.prod: visual-studio-dev15
55
ms.technology: vs-ide-test
66
ms.topic: conceptual
77
ms.topic: conceptual
8-
helpviewer_keywords:
8+
helpviewer_keywords:
99
- "Visual Studio ALM"
1010
- "Live Unit Testing"
1111
author: rpetrusha
1212
ms.author: "ronpet"
13-
ms.workload:
13+
ms.workload:
1414
- "dotnet"
1515
---
1616
# Get started with Live Unit Testing in Visual Studio
@@ -36,7 +36,7 @@ Begin by creating a Visual Studio solution named `UtilityLibraries` that consist
3636

3737
The solution is just a container for one or more projects. To create the solution, open Visual Studio 2017 and do the following:
3838

39-
1. Select **File**, **New**, **Project** from the top-level Visual Studio menu.
39+
1. Select **File** > **New** > **Project** from the top-level Visual Studio menu.
4040

4141
1. In the **New Project** dialog, expand the **Other Project Types** node and select **Visual Studio Solutions**. Select the **Blank Solution** template in the right pane and enter `UtilityLibraries` in the **Name** text box, as the following figure shows:
4242

@@ -47,7 +47,7 @@ The solution is just a container for one or more projects. To create the solutio
4747
Now that you've created the solution, you'll create a class library named `StringLibrary` that contains a number of extension methods for working with strings.
4848

4949
# [C#](#tab/csharp)
50-
1. In **Solution Explorer**, right-click on the `UtilityLibraries` solution and select **Add**, **New Project**.
50+
1. In **Solution Explorer**, right-click on the `UtilityLibraries` solution and select **Add** > **New Project**.
5151

5252
1. In the **Add New Project** dialog, select the C# node, then select **.NET Standard**.
5353

@@ -75,7 +75,7 @@ Now that you've created the solution, you'll create a class library named `Strin
7575
1. Select **Build**, **Build Solution** from the top-level Visual Studio menu. Visual Studio should successfully build your library.
7676

7777
# [Visual Basic](#tab/visual-basic)
78-
1. In **Solution Explorer**, right-click on the `UtilityLibraries` solution and select **Add**, **New Project**.
78+
1. In **Solution Explorer**, right-click on the `UtilityLibraries` solution and select **Add** > **New Project**.
7979

8080
1. In the **Add New Project** dialog, select the Visual Basic node, then select **.NET Standard**.
8181

@@ -113,7 +113,7 @@ Now that you've created the solution, you'll create a class library named `Strin
113113
The next step is to create the unit test project to test `StringLibrary` library. Create the unit tests by performing the following steps:
114114

115115
# [C#](#tab/csharp)
116-
1. In **Solution Explorer**, right-click on the `UtilityLibraries` solution and select **Add**, **New Project**.
116+
1. In **Solution Explorer**, right-click on the `UtilityLibraries` solution and select **Add** > **New Project**.
117117

118118
1. In the **Add New Project** dialog, select the C# node, then select **.NET Core**.
119119

@@ -151,7 +151,7 @@ The next step is to create the unit test project to test `StringLibrary` library
151151

152152
# [Visual Basic](#tab/visual-basic)
153153

154-
1. In **Solution Explorer**, right-click on the `UtilityLibraries` solution and select **Add**, **New Project**.
154+
1. In **Solution Explorer**, right-click on the `UtilityLibraries` solution and select **Add** > **New Project**.
155155

156156
1. In the **Add New Project** dialog, select the Visual Basic node, then select **.NET Core**.
157157

0 commit comments

Comments
 (0)