Merge pull request #4443 from MicrosoftDocs/master

4/15/2019 AM Publish

Author: Taojunshen

docs/debugger/debugging-basics-registers-window.md

@@ -40,8 +40,24 @@ The **Registers** window is available only if address-level debugging is enabled
 
  The **Registers** window enables you to do more than just view the contents of a register. When you are in break mode in native code, you can click on the contents of a register and edit the value. This is not something you should do at random. Unless you understand the register you are editing, and the data it contains, the result of careless editing is likely to be a program crash or some other undesired consequence. Unfortunately, a detailed explanation of the register sets of the various Intel and Intel-compatible processors goes far beyond the scope of this brief introduction.
 
-## Register Groups
- To reduce clutter, the **Registers** window organizes registers into groups. If you right-click on the **Registers** window, you will see a shortcut menu containing a list of groups, which you can display or hide as you see fit.
+## Register groups
+
+To reduce clutter, the **Registers** window organizes registers into groups. If you right-click on the **Registers** window, you will see a shortcut menu containing a list of groups, which you can display or hide as you see fit.
+
+## Register flags
+
+For Intel x86 processors, you may see the following flags in the **Registers** window. During a debugging session, you can also edit these flags.
+
+|Flag|Set value|
+|-|-|
+|Overflow|OV = 1|
+|Direction|UP = 1|
+|Interrupt|EI = 1|
+|Sign|PL = 1|
+|Zero|ZR = 1|
+|Auxiliary carry|AC = 1|
+|Parity|PE = 1|
+|Carry|CY = 1|
 
 ## See Also
 - [How to: Use the Registers Window](../debugger/how-to-use-the-registers-window.md)

docs/debugger/how-to-use-the-registers-window.md

@@ -36,6 +36,8 @@ During debugging, register values change as code executes in your app. Values th
 
 To reduce clutter, the **Registers** window organizes registers into groups, which vary according to platform and processor type. You can display or hide register groups. For more information, see [How to: Display and hide register groups](../debugger/how-to-display-and-hide-register-groups.md).
 
+For info on the flags you see in the **Registers** window, see [About the Registers window](../debugger/debugging-basics-registers-window.md)
+
 You can edit register values. For more information, see [How to: Edit a register value](../debugger/how-to-edit-a-register-value.md).
 
 **To open the Registers window**

docs/debugger/walkthrough-writing-a-visualizer-in-csharp.md

@@ -1,7 +1,7 @@
 ---
 title: "Write a visualizer in C# | Microsoft Docs"
 ms.custom: "seodec18"
-ms.date: "08/01/2018"
+ms.date: "04/12/2019"
 ms.topic: "conceptual"
 dev_langs:
   - "CSharp"
@@ -29,15 +29,16 @@ Follow the tasks below to create a visualizer.
 
 ### To create a class library project
 
-1. On the **File** menu, choose **New > Project**.
-
-2. In the **New Project** dialog box, under **Visual C#**, and then select **.NET Standard**.
-
-3. In the middle pane, choose **Class Library**.
+1. Create a new class library project.
 
-4. In the **Name** box, type an appropriate name for the class library, such as MyFirstVisualizer.
+    ::: moniker range=">=vs-2019"
+    Press **Esc** to close the start window. Type **Ctrl + Q** to open the search box, type **class library**, choose **Templates**, then choose **Create a new Class Library (.NET Standard)**. In the dialog box that appears, choose **Create**.
+    ::: moniker-end
+    ::: moniker range="vs-2017"
+    From the top menu bar, choose **File** > **New** > **Project**. In the left pane of the **New project** dialog box, under **Visual C#**, choose **.NET Standard**, and then in the middle pane choose **Class Library (.NET Standard)**.
+    ::: moniker-end
 
-5. Click **OK**.
+2. Type an appropriate name for the class library, such as `MyFirstVisualizer`, and then click **Create** or **OK**.
 
    After you have created the class library, you must add a reference to Microsoft.VisualStudio.DebuggerVisualizers.DLL so that you can use the classes defined there. Before you add the reference, however, you must rename some classes so that they have meaningful names.
 
@@ -52,7 +53,9 @@ Follow the tasks below to create a visualizer.
 
 3. In **Solution Explorer**, right-click **References** and choose **Add Reference** on the shortcut menu.
 
-4. In the **Add Reference** dialog box, on the **.NET** tab, choose Microsoft.VisualStudio.DebuggerVisualizers.DLL.
+4. In the **Add Reference** dialog box, on the **Browse** tab, select **Browse** and find the Microsoft.VisualStudio.DebuggerVisualizers.DLL.
+
+    You can find the DLL in *\<Visual Studio Install Directory>\Common7\IDE\PublicAssemblies* subdirectory of Visual Studio's installation directory.
 
 5. Click **OK**.
 
@@ -96,7 +99,9 @@ Follow the tasks below to create a visualizer.
 
 1. In **Solution Explorer**, right-click **References** and choose **Add Reference** on the shortcut menu.
 
-2. In the **Add Reference** dialog box, on the **.NET** tab, choose System.Windows.Forms.DLL.
+2. In the **Add Reference** dialog box, on the **Browse** tab, select **Browse**, and find the System.Windows.Forms.DLL.
+
+    You can find the DLL in *C:\Windows\Microsoft.NET\Framework\v4.0.30319*.
 
 3. Click **OK**.
 
@@ -156,21 +161,24 @@ Follow the tasks below to create a visualizer.
 
 ### To add a console application project to the solution
 
-1. On the **File** menu, choose **Add** and then click **New Project**.
-
-2. In the **Add New Project** dialog box, choose **Visual C#** > **Windows Desktop**, and then choose **Console Application**.
+1. In Solution Explorer, right-click the solution, choose **Add**, and then click **New Project**.
 
-3. In the **Name** box, type a meaningful name for the console application, such as `MyTestConsole`.
+    ::: moniker range=">=vs-2019"
+    In the Search box, type **console app**, choose **Templates**, then choose **Create a new Console App (.NET Framework)**. In the dialog box that appears, choose **Create**.
+    ::: moniker-end
+    ::: moniker range="vs-2017"
+    From the top menu bar, choose **File** > **New** > **Project**. In the left pane of the **New project** dialog box, under **Visual C#**, choose **Windows Desktop**, and then in the middle pane choose **Console App (.NET Framework)**.
+    ::: moniker-end
 
-4. Click **OK**.
+2. Type an appropriate name for the class library, such as `MyTestConsole`, and then click **Create** or **OK**.
 
    Now, you must add the necessary references so MyTestConsole can call MyFirstVisualizer.
 
 ### To add necessary references to MyTestConsole
 
 1. In **Solution Explorer**, right-click **MyTestConsole** and choose **Add Reference** on the shortcut menu.
 
-2. In the **Add Reference** dialog box, **.NET** tab, choose Microsoft.VisualStudio.DebuggerVisualizers.DLL.
+2. In the **Add Reference** dialog box, **Browse** tab, choose Microsoft.VisualStudio.DebuggerVisualizers.DLL.
 
 3. Click **OK**.
 

docs/debugger/walkthrough-writing-a-visualizer-in-visual-basic.md

@@ -1,7 +1,7 @@
 ---
 title: "Write a visualizer in Visual Basic | Microsoft Docs"
 ms.custom: "seodec18"
-ms.date: "11/04/2016"
+ms.date: "04/12/2019"
 ms.topic: "conceptual"
 dev_langs:
   - "CSharp"
@@ -30,15 +30,16 @@ Visualizer code must be placed in a DLL that will be read by the debugger. The f
 
 ### To create a class library project
 
-1. On the **File** menu, choose **New** and click **New Project**.
+1. Create a new class library project.
 
-2. In the **New Project** dialog box, select **Visual Basic**.
+    ::: moniker range=">=vs-2019"
+    Press **Esc** to close the start window. Type **Ctrl + Q** to open the search box, type **visual basic**, choose **Templates**, then choose **Create a new Class Library (.NET Standard)**. In the dialog box that appears, choose **Create**.
+    ::: moniker-end
+    ::: moniker range="vs-2017"
+    From the top menu bar, choose **File** > **New** > **Project**. In the left pane of the **New project** dialog box, under **Visual Basic**, choose **.NET Standard**, and then in the middle pane choose **Class Library (.NET Standard)**.
+    ::: moniker-end
 
-3. Under **.NET Standard**, click **Class Library**.
-
-4. In the **Name** box, type an appropriate name for the class library, such as **MyFirstVisualizer**.
-
-5. Click **OK**.
+2. Type an appropriate name for the class library, such as `MyFirstVisualizer`, and then click **Create** or **OK**.
 
    When you have created the class library, you must add a reference to Microsoft.VisualStudio.DebuggerVisualizers.DLL, so that you can use the classes defined there. First, however, you give your project a meaningful name.
 
@@ -53,7 +54,9 @@ Visualizer code must be placed in a DLL that will be read by the debugger. The f
 
 3. In **Solution Explorer**, right-click **My First Visualizer**, and on the shortcut menu, click **Add Reference**.
 
-4. In the **Add Reference** dialog box, on the **.NET** tab, click Microsoft.VisualStudio.DebuggerVisualizers.DLL.
+4. In the **Add Reference** dialog box, on the **Browse** tab, select **Browse** and find the Microsoft.VisualStudio.DebuggerVisualizers.DLL.
+
+    You can find the DLL in *\<Visual Studio Install Directory>\Common7\IDE\PublicAssemblies* subdirectory of Visual Studio's installation directory.
 
 5. Click **OK**.
 
@@ -99,7 +102,9 @@ Visualizer code must be placed in a DLL that will be read by the debugger. The f
 
 1.  In **Solution Explorer**, right-click **References**, and on the shortcut menu, click **Add Reference**.
 
-2.  In the **Add Reference** dialog box, on the **.NET** tab, click **System.Windows.Forms**.
+2. In the **Add Reference** dialog box, on the **Browse** tab, select **Browse**, and find the System.Windows.Forms.DLL.
+
+    You can find the DLL in *C:\Windows\Microsoft.NET\Framework\v4.0.30319*.
 
 3.  Click **OK**.
 
@@ -157,21 +162,24 @@ Visualizer code must be placed in a DLL that will be read by the debugger. The f
 
 ### To add a console application project to the solution
 
-1. On the **File** menu, click **Add**, and then click **New Project**.
-
-2. In the **Add New Project** dialog box, select **Visual Basic**, and then click **Console Application**.
+1. In Solution Explorer, right-click the solution, choose **Add**, and then click **New Project**.
 
-3. In the **Name** box, type a meaningful name for the console application, such as **MyTestConsole**.
+    ::: moniker range=">=vs-2019"
+    In the Search box, type **visual basic**, choose **Templates**, then choose **Create a new Console App (.NET Framework)**. In the dialog box that appears, choose **Create**.
+    ::: moniker-end
+    ::: moniker range="vs-2017"
+    From the top menu bar, choose **File** > **New** > **Project**. In the left pane of the **New project** dialog box, under **Visual Basic**, choose **Windows Desktop**, and then in the middle pane choose **Console App (.NET Framework)**.
+    ::: moniker-end
 
-4. Click **OK**.
+2. Type an appropriate name for the class library, such as `MyTestConsole`, and then click **Create** or **OK**.
 
    Now, you must add the necessary references so MyTestConsole can call MyFirstVisualizer.
 
 ### To add necessary references to MyTestConsole
 
 1.  In **Solution Explorer**, right-click **MyTestConsole**, and on the shortcut menu, click **Add Reference**.
 
-2.  In the **Add Reference** dialog box, on the **.NET** tab, click Microsoft.VisualStudio.DebuggerVisualizers.
+2.  In the **Add Reference** dialog box, on the **Browse** tab, click Microsoft.VisualStudio.DebuggerVisualizers.
 
 3.  Click **OK**.
 

docs/javascript/create-application-with-vuejs.md

@@ -92,6 +92,9 @@ To install the vue-cli npm module, open a command prompt and type `npm install -
 
 1. Type `vue init webpack ClientApp` and follow steps when prompted to answer additional questions.
 
+    > [!NOTE]
+    > For *.vue* files, you need to use WebPack or a similar framework with a loader to do the conversion. TypeScript and Visual Studio does not know how to compile *.vue* files. The same is true for bundling; TypeScript doesn't know how to convert ES2015 modules (that is, `import` and `export` statements) into a single final *.js* file to load in the browser. Again, WebPack is the best choice here. To drive this process from within Visual Studio using MSBuild, you need to do start from a Visual Studio template. At present, there is no ASP.NET template for Vue.js development in-the-box.
+
 #### Modify the webpack configuration to output the built files to wwwroot
 
 * Open the file *./ClientApp/config/index.js*, and change the `build.index` and `build.assetsRoot` to wwwroot path:

docs/msbuild/common-msbuild-project-properties.md

@@ -48,7 +48,7 @@ The following table lists frequently used properties that are defined in the Vis
 | CscToolPath | The path of *csc.exe*, the [!INCLUDE[csprcs](../data-tools/includes/csprcs_md.md)] compiler. |
 | CustomBeforeMicrosoftCommonTargets | The name of a project file or targets file that is to be imported automatically before the common targets import. |
 | DebugSymbols | A boolean value that indicates whether symbols are generated by the build.<br /><br /> Setting **-p:DebugSymbols=false** on the command line disables generation of program database (*.pdb*) symbol files. |
-| DebugType | Defines the level of debug information that you want generated. Valid values are "full," "pdbonly," and "none." |
+| DebugType | Defines the level of debug information that you want generated. Valid values are "full," "pdbonly," "portable", "embedded", and "none." |
 | DefineConstants | Defines conditional compiler constants. Symbol/value pairs are separated by semicolons and are specified by using the following syntax:<br /><br /> *symbol1 = value1 ; symbol2 = value2*<br /><br /> The property is equivalent to the `/define` compiler switch. |
 | DefineDebug | A boolean value that indicates whether you want the DEBUG constant defined. |
 | DefineTrace | A boolean value that indicates whether you want the TRACE constant defined. |

docs/msbuild/customize-your-build.md

@@ -12,7 +12,7 @@ manager: jillfra
 ms.workload:
   - "multiple"
 ---
-# Customize your build (C#, F#, Visual Basic)
+# Customize your build
 
 MSBuild projects that use the standard build process (importing *Microsoft.Common.props* and *Microsoft.Common.targets*) have several extensibility hooks that you can use to customize your build process.