Merge pull request #4187 from gregvanl/vssdk-preview

Update your first extension tutorial for Dev16

Author: rmca14

docs/extensibility/extensibility-hello-world.md

@@ -1,6 +1,6 @@
 ---
 title: "Hello World extension tutorial | Microsoft Docs"
-ms.date: "07/10/2017"
+ms.date: "03/14/2019"
 ms.topic: "conceptual"
 ms.assetid: f74e1ad1-1ee5-4360-9bd5-d82467b884ca
 author: "gregvanl"
@@ -29,53 +29,75 @@ For this example, you'll use Visual C# to add a custom menu button named "Say He
 
 ## Prerequisites
 
-Before you start, make sure you have installed the **Visual Studio extension development** workload which includes the VSIX template you'll need and sample code.
+Before you start, make sure you have installed the **Visual Studio extension development** workload, which includes the VSIX template you'll need and sample code.
 
 > [!NOTE]
 > You can use any edition of Visual Studio (Community, Professional, or Enterprise) to create a Visual Studio extensibility project.
 
 ## Create an extensibility project
 
-Step 1. From the **File** menu, click **New Project**. At the bottom of the screen, enter the name of your project.
+::: moniker range="vs-2017"
+
+Step 1. From the **File** menu, select **New Project**.
 
-Step 2. From the **Templates** menu, click **Visual C#**, click **Extensibility**, and then click **VSIX Project**.
+Step 2. In the search box in the upper right, type "vsix" and select the Visual C# **VSIX Project**. Enter "HelloWorld" for the **Name** at the bottom of the dialog and select **OK**.
 
 ![new project](media/hello-world-new-project.png)
 
 You should now see the Getting Started page and some sample resources.
 
-::: moniker range="vs-2017"
-
 If you need to leave this tutorial and come back to it, you can find your new HelloWorld project on the **Start Page** in the **Recent** section.
 
 ::: moniker-end
 
+::: moniker range=">=vs-2019"
+
+Step 1. From the **File** menu, select **New Project**. Search for "vsix" and select the Visual C# **VSIX Project** and then **Next**.
+
+Step 2. Enter "HelloWorld" for the **Project name** and select **Create**.
+
+![new project](media/hello-world-new-project-2019.png)
+
+You should now see the HelloWorld project in **Solution Explorer**.
+
+::: moniker-end
+
 ## Add a custom command
 
-Step 1. If you select the manifest, you can see what options are changeable, for instance, metadata, description, and version.
+Step 1. If you select the *.vsixmanifest* manifest file, you can see what options are changeable, such as description, author, and version.
 
-Step 2. Right-click the project (not the solution). On the context menu, click **Add**, and then click **New Item**.
+Step 2. Right-click the project (not the solution). On the context menu, select **Add**, and then **New Item**.
 
-Step 3. Select the **Extensibility** section, and then click **Custom Command**.
+Step 3. Select the **Extensibility** section, and then choose **Custom Command**.
 
-Step 4. In the **Name** field at the bottom, give it a name, for instance *Command.cs*.
+Step 4. In the **Name** field at the bottom, enter a filename such as *Command.cs*.
 
 ![custom command](media/hello-world-custom-command.png)
 
-Your new command is listed in **Solution Explorer** under the **Resources** branch. This is also where you'll find other files related to your command, such as the PNG and ICO files if you wish to modify the image.
+Your new command file is visible in **Solution Explorer**. Under the **Resources** node, you'll find other files related to your command. For example, if you wish to modify the image, the PNG file is here.
 
 ## Modify the source code
 
-At this point, the Button you're adding is pretty generic. You'll have to modify the VSCT file and CS file if you want to make changes.
+At this point, the command and Button text is auto-generated and not very interesting. You can modify the VSCT file and CS file if you want to make changes.
 
-* The VSCT file is where you can rename your commands, as well as define where they go in the Visual Studio command system. As you explore the VSCT file, you will notice a lot of commented code that explains what each section of code controls.
+* The VSCT file is where you can rename your commands, as well as define where they go in the Visual Studio command system. As you explore the VSCT file, you will notice comments that explain what each section of the VSCT code controls.
 
 * The CS file is where you can define actions, such as the click handler.
 
+::: moniker range="vs-2017"
+
 Step 1. In **Solution Explorer**, find the VSCT file for your new command. In this case, it will be called *CommandPackage.vsct*.
 
 ![command package vsct](media/hello-world-command-package-vsct.png)
 
+::: moniker-end
+
+::: moniker range=">=vs-2019"
+
+Step 1. In **Solution Explorer**, find the VSCT file for your extension VS package. In this case, it will be called *HelloWorldPackage.vsct*.
+
+::: moniker-end
+
 Step 2. Change the `ButtonText` parameter to `Say Hello World!`.
 
 ```xml
@@ -90,14 +112,15 @@ Step 2. Change the `ButtonText` parameter to `Say Hello World!`.
   ...
 ```
 
-Step 3. Go back to **Solution Explorer** and find the *Command.cs* file. Change the string `message` for the command `string.Format(..)` to `Hello World!`.
+Step 3. Go back to **Solution Explorer** and find the *Command.cs* file. In the `Execute` method, change the string `message` from `string.Format(..)` to `Hello World!`.
 
 ```csharp
   ...
-  private void MenuItemCallback(object sender, EventArgs e)
+  private void Execute(object sender, EventArgs e)
   {
+    ThreadHelper.ThrowIfNotOnUIThread();
     string message = "Hello World!";
-    string title = "Command1";
+    string title = "Command";
 
     // Show a message box to prove we were here
     VsShellUtilities.ShowMessageBox(
@@ -117,12 +140,16 @@ Make sure to save your changes to each file.
 
 You can now run the source code in the Visual Studio Experimental Instance.
 
-Step 1. Click **Start** in the Toolbar. This builds your project and starts the debugger, launching a new instance of Visual Studio called the **Experimental Instance**.
+Step 1. Press **F5** to run the **Start Debugging** command. This command builds your project and starts the debugger, launching a new instance of Visual Studio called the **Experimental Instance**.
+
+::: moniker range="vs-2017"
 
 You will see the words **Experimental Instance** in the Visual Studio title bar.
 
 ![experimental instance title bar](media/hello-world-exp-instance.png)
 
+::: moniker-end
+
 Step 2. On the **Tools** menu of the **Experimental Instance**, click **Say Hello World!**.
 
 ![final result](media/hello-world-final-result.png)
@@ -134,5 +161,6 @@ You should see the output from your new custom command, in this case the dialog
 Now that you know the basics of working with Visual Studio Extensibility, here's where you can learn more:
 
 * [Start to develop Visual Studio extensions](starting-to-develop-visual-studio-extensions.md) - Samples, tutorials. and publishing your extension
-* [What's new in the Visual Studio 2017 SDK](what-s-new-in-the-visual-studio-2017-sdk.md) -New extensibility features in Visual Studio 2017
+* [What's new in the Visual Studio 2017 SDK](what-s-new-in-the-visual-studio-2017-sdk.md) - New extensibility features in Visual Studio 2017
+* [What's new in the Visual Studio 2019 SDK](whats-new-visual-studio-2019-sdk.md) - New extensibility features in Visual Studio 2019
 * [Inside the Visual Studio SDK](internals/inside-the-visual-studio-sdk.md) - Learn the details of Visual Studio Extensibility