MicrosoftDocs · gewarren · Mar 15, 2019 · Feb 26, 2019 · Mar 8, 2019 · Mar 13, 2019
diff --git a/docs/cross-platform/build-an-opengl-es-application-on-android-and-ios.md b/docs/cross-platform/build-an-opengl-es-application-on-android-and-ios.md
@@ -25,11 +25,9 @@ Before you can create an OpenGL ES app for iOS and Android, you must make sure y
 
 In this tutorial, you first create a new OpenGL ES Application project and then build and run the default app in the Visual Studio Emulator for Android. Next you build the app for iOS and run the app in the iOS Simulator.
 
-### To create a new project
+1. In Visual Studio, choose **File** > **New** > **Project**.
 
-1. Open Visual Studio. On the menu bar, choose **File**, **New**, **Project**.
-
-2. In the **New Project** dialog box, under **Templates**, choose **Visual C++**, **Cross Platform**, and then choose the **OpenGLES Application (Android, iOS)** template.
+2. In the **New Project** dialog box, under **Templates**, choose **Visual C++** > **Cross Platform**, and then choose the **OpenGLES Application (Android, iOS)** template.
 
 3. Give the app a name like `MyOpenGLESApp`, and then choose **OK**.
 

diff --git a/docs/cross-platform/create-an-android-native-activity-app.md b/docs/cross-platform/create-an-android-native-activity-app.md
@@ -25,9 +25,7 @@ Before you can create an Android Native Activity app, you must make sure you've
 
 In this tutorial, you'll first create a new Android Native Activity project and then build and run the default app in the Visual Studio Emulator for Android.
 
-### To create a new project
-
-1. Open Visual Studio. On the menu bar, choose **File** > **New** > **Project**.
+1. In Visual Studio, choose **File** > **New** > **Project**.
 
 2. In the **New Project** dialog box, under **Templates**, choose **Visual C++** > **Cross Platform**, and then choose the **Native-Activity Application (Android)** template.
 

diff --git a/docs/cross-platform/cross-platform-mobile-development-in-visual-studio.md b/docs/cross-platform/cross-platform-mobile-development-in-visual-studio.md
@@ -90,7 +90,7 @@ With Visual Studio Tools for Xamarin, you can target Android, iOS, and Windows i
 
  ![Multi-device hybrid apps with Javascript](../cross-platform/media/multidevicehybridapps.png "Multi-device hybrid apps with Javascript")
 
- To get started, install Visual Studio 2017 and choose the **Mobile Development with Javascript** feature during setup. The Cordova tools automatically install all third-party software that's required to build your multi-platform app.
+ To get started, install Visual Studio and choose the **Mobile Development with Javascript** feature during setup. The Cordova tools automatically install all third-party software that's required to build your multi-platform app.
 
  After you've installed the extension, open Visual Studio and create a **Blank App (Apache Cordova)** project. Then, you can develop your app by using JavaScript or Typescript. You can also add plug-ins to extend the functionality of your app, and APIs from plug-ins appear in IntelliSense as you write code.
 

diff --git a/docs/cross-platform/install-visual-cpp-for-cross-platform-mobile-development.md b/docs/cross-platform/install-visual-cpp-for-cross-platform-mobile-development.md
@@ -65,7 +65,7 @@ The Visual Studio Installer for Visual Studio 2017 includes a **Mobile developme
    > [!IMPORTANT]
    > You must restart to make sure everything is installed correctly.
 
-1. Open Visual Studio. If this is the first time that you have run Visual Studio, it may take some time to configure and sign in. When Visual Studio is ready, check for any updates and install them.
+1. Open Visual Studio.
 
 > [!NOTE]
 > If you're using Visual Studio 2015, see [Install Visual C++ for Cross-Platform Mobile Development (Visual Studio 2015)](/cross-platform/install-visual-cpp-for-cross-platform-mobile-development?view=vs-2015)

diff --git a/docs/data-tools/bind-wpf-controls-to-a-dataset.md b/docs/data-tools/bind-wpf-controls-to-a-dataset.md
@@ -50,16 +50,30 @@ Prior knowledge of the following concepts is also helpful, but not required to c
 
 Create a new WPF project to display product records.
 
-1. Start Visual Studio.
+::: moniker range="vs-2017"
+
+1. Open Visual Studio.
 
 2. On the **File** menu, select **New** > **Project**.
 
 3. Expand **Visual Basic** or **Visual C#**, and then select **Windows**.
 
-4. Select the **WPF Application** project template.
+4. Select the **WPF App** project template.
 
 5. In the **Name** box, enter **AdventureWorksProductsEditor** and then select **OK**.
 
+::: moniker-end
+
+::: moniker range=">=vs-2019"
+
+1. Open Visual Studio.
+
+2. On the Start window, choose **Create a new project**.
+
+3. Search for the C# **WPF App** project template and follow the steps to create the project, naming the project **AdventureWorksProductsEditor**.
+
+::: moniker-end
+
    Visual Studio creates the AdventureWorksProductsEditor project.
 
 ## Create a dataset for the application

diff --git a/docs/data-tools/bind-wpf-controls-to-a-wcf-data-service.md b/docs/data-tools/bind-wpf-controls-to-a-wcf-data-service.md
@@ -44,7 +44,7 @@ You need the following components to complete this walkthrough:
 
 Prior knowledge of the following concepts is also helpful, but not required to complete the walkthrough:
 
-- WCF Data Services. For more information, see [Overview](/dotnet/framework/data/wcf/wcf-data-services-overview).
+- [WCF Data Services](/dotnet/framework/data/wcf/wcf-data-services-overview).
 
 - Data models in [!INCLUDE[ssAstoria](../data-tools/includes/ssastoria_md.md)].
 
@@ -54,21 +54,9 @@ Prior knowledge of the following concepts is also helpful, but not required to c
 
 ## Create the service project
 
-Start this walkthrough by creating a project for a WCF Data Service:
+1. Start this walkthrough by creating a C# or Visual Basic **ASP.NET Web Application** project. Name the project **AdventureWorksService**.
 
-1. Start Visual Studio.
-
-2. On the **File** menu, point to **New**, and then click **Project**.
-
-3. Expand **Visual C#** or **Visual Basic**, and then select **Web**.
-
-4. Select the **ASP.NET Web Application** project template.
-
-5. In the **Name** box, type **AdventureWorksService** and click **OK**.
-
-     Visual Studio creates the **AdventureWorksService** project.
-
-6. In **Solution Explorer**, right-click **Default.aspx** and select **Delete**. This file is not necessary in this walkthrough.
+2. In **Solution Explorer**, right-click **Default.aspx** and select **Delete**. This file is not necessary for the walkthrough.
 
 ## Create an Entity Data Model for the service
 

diff --git a/docs/designers/how-to-build-and-run-the-linqtoxmldatabinding-example.md b/docs/designers/how-to-build-and-run-the-linqtoxmldatabinding-example.md
@@ -14,11 +14,9 @@ This topic shows how to create and build the LinqToXmlDataBinding Visual Studio
 
 For more information about Visual Studio, see [Visual Studio IDE overview](../get-started/visual-studio-ide.md).
 
-## Create and populate the project
+## Create the project
 
-### To create the starting project
-
-1. Start Visual Studio and create a C# WPF application named LinqToXmlDataBinding. The project must use the .NET Framework 3.5 (or later).
+1. Open Visual Studio and create a C# **WPF App** named **LinqToXmlDataBinding**. The project should target the .NET Framework 3.5 (or later).
 
 1. If not already present, add project references for the following .NET assemblies:
 
@@ -32,9 +30,9 @@ For more information about Visual Studio, see [Visual Studio IDE overview](../ge
 
 1. Build the solution by pressing **Ctrl**+**Shift**+**B**, then run it by pressing **F5**. The project should compile without errors and run as a generic WPF application.
 
-### To add custom code to the project
+## Add code to the project
 
-1. In Solution Explorer, rename the source file **Window1.xaml** to **L2XDBForm.xaml**. The dependent source file **Window1.xaml.cs** should automatically be renamed to **L2XDBForm.xaml.cs**.
+1. In **Solution Explorer**, rename the source file **Window1.xaml** to **L2XDBForm.xaml**. The dependent source file **Window1.xaml.cs** should automatically be renamed to **L2XDBForm.xaml.cs**.
 
 1. Replace the source code found in the file **L2XDBForm.xaml** with the code section from the topic [L2DBForm.xaml source code](../designers/l2dbform-xaml-source-code.md). Use the XAML source view to work with this file.
 
@@ -50,9 +48,7 @@ The LinqToXmlDataBinding program enables the user to view and manipulate a list
 
 ### To run the program and view the book list
 
-- Run LinqToXmlDataBinding by pressing **F5** (**Start Debugging**) or **Ctrl**+**F5** (**Start Without Debugging**).
-
-   A program window with the title **WPF Data Binding using LINQ to XML** appears.
+Run LinqToXmlDataBinding by pressing **F5** (**Start Debugging**) or **Ctrl**+**F5** (**Start Without Debugging**). A program window with the title **WPF Data Binding using LINQ to XML** appears.
 
 - Notice the top section of the UI, which displays the raw **XML** that represents the book list. It is displayed using a WPF <xref:System.Windows.Controls.TextBlock> control, which does not enable interaction through the mouse or keyboard.
 

diff --git a/docs/get-started/csharp/tutorial-editor.md b/docs/get-started/csharp/tutorial-editor.md
@@ -29,9 +29,21 @@ This article assumes you're already familiar with C#. If you aren't, we suggest
 
 Start by creating a new file and adding some code to it.
 
-1. Open Visual Studio, and from the **File** menu on the menu bar, choose **New** > **File**.
+::: moniker range="vs-2017"
 
-1. In the **New File** dialog box, under the **General** category, choose **Visual C# Class**, and then choose **Open**.
+1. Open Visual Studio.
+
+::: moniker-end
+
+::: moniker range=">=vs-2019"
+
+1. Open Visual Studio. Press **Esc** or click **Continue without code** on the Start window to open the development environment.
+
+::: moniker-end
+
+2. From the **File** menu on the menu bar, choose **New** > **File**.
+
+3. In the **New File** dialog box, under the **General** category, choose **Visual C# Class**, and then choose **Open**.
 
    A new file opens in the editor with the skeleton of a C# class. (Notice that we don't have to create a full Visual Studio project to gain some of the benefits that the code editor offers; all you need is a code file!)
 

diff --git a/docs/get-started/csharp/tutorial-projects-solutions.md b/docs/get-started/csharp/tutorial-projects-solutions.md
@@ -32,9 +32,11 @@ Despite its name, a solution is not an "answer". A solution is simply a containe
 
 We'll start our exploration by creating an empty solution. After you get to know Visual Studio, you probably won't find yourself creating empty solutions very often. When you create a new project, Visual Studio automatically creates a solution to house the project if there's not a solution already open.
 
+::: moniker range="vs-2017"
+
 1. Open Visual Studio.
 
-1. On the menu bar, which is the row of menus such as **File** and **Edit**, choose **File** > **New** > **Project**.
+1. On the top menu bar, choose **File** > **New** > **Project**.
 
    The **New Project** dialog box opens.
 
@@ -44,6 +46,22 @@ We'll start our exploration by creating an empty solution. After you get to know
 
    The **Start Page** closes, and a solution appears in **Solution Explorer** on the right-hand side of the Visual Studio window. You'll probably use **Solution Explorer** often, to browse the contents of your projects.
 
+::: moniker-end
+
+::: moniker range=">=vs-2019"
+
+1. Open Visual Studio.
+
+2. On the Start window, choose **Create a new project**.
+
+3. On the **Create a new project** page, enter **blank solution** into the search box, select the **Blank Solution** template, and then choose **Next**.
+
+4. Name the solution **QuickSolution**, and then choose **Create**.
+
+   A solution appears in **Solution Explorer** on the right-hand side of the Visual Studio window. You'll probably use **Solution Explorer** often, to browse the contents of your projects.
+
+::: moniker-end
+
 ### Add a project
 
 Now let's add our first project to the solution. We'll start with an empty project and add the items we need to the project.

diff --git a/docs/get-started/includes/ide-overview.md b/docs/get-started/includes/ide-overview.md
@@ -150,7 +150,7 @@ To get started, [download Visual Studio](https://visualstudio.microsoft.com/down
 
 ![.NET Core cross-platform development workload in Visual Studio Installer](../media/dotnet-core-cross-platform-workload.png)
 
-When you start Visual Studio for the first time, you can optionally [sign in](../../ide/signing-in-to-visual-studio.md) using your Microsoft account or your work or school account.
+When you open Visual Studio for the first time, you can optionally [sign in](../../ide/signing-in-to-visual-studio.md) using your Microsoft account or your work or school account.
 
 ## Create a program
 

diff --git a/docs/get-started/tutorial-editor.md b/docs/get-started/tutorial-editor.md
@@ -25,9 +25,21 @@ This article assumes you're already familiar with a programming language. If you
 
 Start by creating a new file and adding some code to it.
 
-1. Open Visual Studio, and from the **File** menu on the menu bar, choose **New** > **File**.
+::: moniker range="vs-2017"
 
-1. In the **New File** dialog box, under the **General** category, choose **Visual C# Class**, and then choose **Open**.
+1. Open Visual Studio.
+
+::: moniker-end
+
+::: moniker range=">=vs-2019"
+
+1. Open Visual Studio. Press **Esc** or click **Continue without code** on the start window to open the development environment.
+
+::: moniker-end
+
+2. From the **File** menu on the menu bar, choose **New** > **File**.
+
+3. In the **New File** dialog box, under the **General** category, choose **Visual C# Class**, and then choose **Open**.
 
    A new file opens in the editor with the skeleton of a C# class. (Notice that we don't have to create a full Visual Studio project to gain some of the benefits that the code editor offers; all you need is a code file!)
 

diff --git a/docs/get-started/tutorial-open-project-from-repo.md b/docs/get-started/tutorial-open-project-from-repo.md
@@ -45,7 +45,7 @@ If you haven't already installed Visual Studio, go to the [Visual Studio downloa
 
     ![Choose Clone from the Local Git Repositories section](./media/open-proj-repo-local-git-repo-clone.png)
 
-1. In the box that says ***Enter the URL of a Git repo to clone***, type or paste the URL for your repo, and then press **Enter**. (You might receive a prompt to sign in to your Git repo; if so, do so.)
+1. In the box that says ***Enter the URL of a Git repo to clone***, type or paste the URL for your repo, and then press **Enter**. (You might receive a prompt to sign in to GitHub; if so, do so.)
 
    After Visual Studio clones your repo, Team Explorer closes and Solution Explorer opens. A message appears that says *Click on Solutions and Folders above to view a list of Solutions*. Choose **Solutions and Folders**.
 

diff --git a/docs/get-started/tutorial-projects-solutions.md b/docs/get-started/tutorial-projects-solutions.md
@@ -29,9 +29,11 @@ Despite its name, a solution is not an "answer". A solution is simply a containe
 
 We'll start our exploration by creating an empty solution. After you get to know Visual Studio, you probably won't find yourself creating empty solutions very often. When you create a new project, Visual Studio automatically creates a solution to house the project if there's not a solution already open.
 
+::: moniker range="vs-2017"
+
 1. Open Visual Studio.
 
-1. On the menu bar, which is the row of menus such as **File** and **Edit**, choose **File** > **New** > **Project**.
+1. On the menu bar, choose **File** > **New** > **Project**.
 
    The **New Project** dialog box opens.
 
@@ -41,6 +43,22 @@ We'll start our exploration by creating an empty solution. After you get to know
 
    The **Start Page** closes, and a solution appears in **Solution Explorer** on the right-hand side of the Visual Studio window. You'll probably use **Solution Explorer** often, to browse the contents of your projects.
 
+::: moniker-end
+
+::: moniker range=">=vs-2019"
+
+1. Open Visual Studio.
+
+2. On the Start window, choose **Create a new project**.
+
+3. On the **Create a new project** page, enter **blank solution** into the search box, select the **Blank Solution** template, and then choose **Next**.
+
+4. Name the solution **QuickSolution**, and then choose **Create**.
+
+   A solution appears in **Solution Explorer** on the right-hand side of the Visual Studio window. You'll probably use **Solution Explorer** often, to browse the contents of your projects.
+
+::: moniker-end
+
 ### Add a project
 
 Now let's add our first project to the solution. We'll start with an empty project and add the items we need to the project.

diff --git a/docs/get-started/visual-basic/tutorial-editor.md b/docs/get-started/visual-basic/tutorial-editor.md
@@ -29,9 +29,21 @@ This article assumes you're already familiar with Visual Basic. If you aren't, w
 
 Start by creating a new file and adding some code to it.
 
-1. Open Visual Studio, and from the **File** menu on the menu bar, choose **New File**.
+::: moniker range="vs-2017"
 
-1. In the **New File** dialog box, under the **General** category, choose **Visual Basic Class**, and then choose **Open**.
+1. Open Visual Studio.
+
+::: moniker-end
+
+::: moniker range=">=vs-2019"
+
+1. Open Visual Studio. Press **Esc** or click **Continue without code** on the start window to open the development environment.
+
+::: moniker-end
+
+2. From the **File** menu on the menu bar, choose **New File**.
+
+3. In the **New File** dialog box, under the **General** category, choose **Visual Basic Class**, and then choose **Open**.
 
    A new file opens in the editor with the skeleton of a Visual Basic class. (You can already notice that you don't have to create a full Visual Studio project to gain some of the benefits that the code editor offers, such as syntax highlighting. All you need is a code file!)
 

diff --git a/docs/get-started/visual-basic/tutorial-projects-solutions.md b/docs/get-started/visual-basic/tutorial-projects-solutions.md
@@ -32,18 +32,36 @@ Despite its name, a solution is not an "answer". A solution is simply a containe
 
 We'll start our exploration by creating an empty solution. After you get to know Visual Studio, you probably won't find yourself creating empty solutions very often. When you create a new project, Visual Studio automatically creates a solution to house the project if there's not a solution already open.
 
+::: moniker range="vs-2017"
+
 1. Open Visual Studio.
 
-1. On the menu bar, which is the row of menus such as **File** and **Edit**, choose **File** > **New** > **Project**.
+1. On the menu bar, choose **File** > **New** > **Project**.
 
    The **New Project** dialog box opens.
 
-1. In the left pane, expand **Other Project Types**, then choose **Visual Studio Solutions**. In the center pane, choose the **Blank Solution** template. Name your solution **QuickSolution**, then choose the **OK** button.
+1. In the left pane, expand **Other Project Types**, then choose **Visual Studio Solutions**. In the center pane, choose the **Blank Solution** template. Name your solution **QuickSolution**, and then choose **OK**.
 
    ![Blank solution template in Visual Studio](../media/tutorial-projects-new-solution.png)
 
    The **Start Page** closes, and a solution appears in **Solution Explorer** on the right-hand side of the Visual Studio window. You'll probably use **Solution Explorer** often, to browse the contents of your projects.
 
+::: moniker-end
+
+::: moniker range=">=vs-2019"
+
+1. Open Visual Studio.
+
+2. On the Start window, choose **Create a new project**.
+
+3. On the **Create a new project** page, enter **blank solution** into the search box, select the **Blank Solution** template, and then choose **Next**.
+
+4. Name the solution **QuickSolution**, and then choose **Create**.
+
+   A solution appears in **Solution Explorer** on the right-hand side of the Visual Studio window. You'll probably use **Solution Explorer** often, to browse the contents of your projects.
+
+::: moniker-end
+
 ### Add a project
 
 Now let's add our first project to the solution. We'll start with an empty project and add the items we need to the project.

diff --git a/docs/get-started/visual-basic/visual-studio-ide.md b/docs/get-started/visual-basic/visual-studio-ide.md
@@ -201,7 +201,7 @@ To get started, [download Visual Studio](https://visualstudio.microsoft.com/down
 
 ![.NET Core cross-platform development workload in Visual Studio Installer](../media/dotnet-core-cross-platform-workload.png)
 
-When you start Visual Studio for the first time, you can optionally [sign in](../../ide/signing-in-to-visual-studio.md) using your Microsoft account or your work or school account.
+When you open Visual Studio for the first time, you can optionally [sign in](../../ide/signing-in-to-visual-studio.md) using your Microsoft account or your work or school account.
 
 ## Customize Visual Studio
 

diff --git a/docs/ide/customizing-the-start-page-for-visual-studio.md b/docs/ide/customizing-the-start-page-for-visual-studio.md
@@ -59,7 +59,7 @@ To install a custom start page, open the *.vsix* file, or copy and paste the sta
 1. In the **Customize Start Page** list, choose the page that you want.
 
 > [!TIP]
-> If an error in a custom start page causes Visual Studio to crash, you can start Visual Studio in safe mode and then set it to use the default start page. See [/SafeMode (devenv.exe)](../ide/reference/safemode-devenv-exe.md).
+> If an error in a custom start page causes Visual Studio to crash, you can open Visual Studio in safe mode and then set it to use the default start page. See [/SafeMode (devenv.exe)](../ide/reference/safemode-devenv-exe.md).
 
 ## See also