Merge pull request #1194 from MicrosoftDocs/FromPublicMaster

Confirm merge from FromPublicMaster to master to sync with https://github.com/MicrosoftDocs/visualstudio-docs (branch master)

Author: Colin Robertson

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

@@ -55,7 +55,7 @@ To begin this tutorial, you need a multithreaded application project. Follow the
 
     ```VB  
     Thread.Sleep(3000)   
-    Console.WriteLine(  
+    Console.WriteLine()
     ```  
 
     ```CSharp  
@@ -259,4 +259,4 @@ You can freeze and thaw (suspend and resume) threads to control the order in whi
 
 ## See Also  
  [Debug Multithreaded Applications](../debugger/debug-multithreaded-applications-in-visual-studio.md)   
- [How to: Switch to Another Thread While Debugging](../debugger/how-to-switch-to-another-thread-while-debugging.md)
+ [How to: Switch to Another Thread While Debugging](../debugger/how-to-switch-to-another-thread-while-debugging.md)

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

@@ -10,9 +10,6 @@ ms.tgt_pltfrm: ""
 ms.topic: "article"
 dev_langs: 
   - "CSharp"
-  - "VB"
-  - "FSharp"
-  - "C++"
 helpviewer_keywords: 
   - "visualizers, writing"
   - "walkthroughs [Visual Studio], visualizers"
@@ -67,7 +64,7 @@ Follow the tasks below to create a visualizer.
 
 6.  In DebuggerSide.cs, add the following statement to the `using` statements:  
 
-    ```  
+    ```csharp  
     using Microsoft.VisualStudio.DebuggerVisualizers;  
     ```  
 
@@ -77,13 +74,13 @@ Follow the tasks below to create a visualizer.
 
 1.  In DebuggerSide.cs, go to the following line of code:  
 
-    ```  
+    ```csharp  
     public class DebuggerSide  
     ```  
 
 2.  Change the code to:  
 
-    ```  
+    ```csharp  
     public class DebuggerSide : DialogDebuggerVisualizer  
     ```  
 
@@ -93,8 +90,8 @@ Follow the tasks below to create a visualizer.
 
 -   In `public class DebuggerSide`, add the following **method:**  
 
-    ```  
-    override protected void Show(IDialogVisualizerService windowService, IVisualizerObjectProvider objectProvider)  
+    ```csharp  
+    protected override void Show(IDialogVisualizerService windowService, IVisualizerObjectProvider objectProvider)  
     {  
     }  
     ```  
@@ -111,7 +108,7 @@ Follow the tasks below to create a visualizer.
 
 4.  In DebuggerSide.cs, add the following statement to the `using` statements:  
 
-    ```  
+    ```csharp  
     using System.Windows.Forms;  
     ```  
 
@@ -121,7 +118,7 @@ Follow the tasks below to create a visualizer.
 
 1.  In the `Show` method, add the following line of code:  
 
-    ```  
+    ```csharp  
     MessageBox.Show(objectProvider.GetObject().ToString());  
     ```  
 
@@ -135,12 +132,12 @@ Follow the tasks below to create a visualizer.
 
 1.  Add the following attribute code to DebuggerSide.cs, after the `using` statements but before `namespace MyFirstVisualizer`:  
 
-    ```  
+    ```csharp  
     [assembly:System.Diagnostics.DebuggerVisualizer(  
     typeof(MyFirstVisualizer.DebuggerSide),  
     typeof(VisualizerObjectSource),  
-    Target  = typeof(System.String),  
-    Description  = "My First Visualizer")]  
+    Target = typeof(System.String),  
+    Description = "My First Visualizer")]  
     ```  
 
 2.  On the **Build** menu, choose **Build MyFirstVisualizer**. The project should build successfully. Correct any build errors before continuing.  
@@ -151,7 +148,7 @@ Follow the tasks below to create a visualizer.
 
 1.  Add the following method to class `public DebuggerSide`:  
 
-    ```  
+    ```csharp  
     public static void TestShowVisualizer(object objectToVisualize)  
     {  
        VisualizerDevelopmentHost visualizerHost = new VisualizerDevelopmentHost(objectToVisualize, typeof(DebuggerSide));  
@@ -201,13 +198,13 @@ Follow the tasks below to create a visualizer.
 
 3.  In TestConsole.cs, add the following code to the `using` statements:  
 
-    ```  
+    ```csharp  
     using MyFirstVisualizer;  
     ```  
 
 4.  In method `Main`, add the following code:  
 
-    ```  
+    ```csharp  
     String myString = "Hello, World";  
     DebuggerSide.TestShowVisualizer(myString);  
     ```  

docs/designers/walkthrough-my-first-wpf-desktop-application2.md

@@ -266,7 +266,7 @@ In this section, you'll create the application infrastructure, which includes th
   
 1.  Choose the following image and save it as `watermark.png`.  
   
-     ![Watermark image for walkthrough](../designers/media/wpf_watermark.png "WPF_watermark")  
+     ![Watermark image for walkthrough](../designers/media/wpf_watermark.png "watermark")  
   
     > [!NOTE]
     >  Alternatively you can create your own image and save it as `watermark.png`.  
@@ -885,4 +885,4 @@ In this section, you'll create the application infrastructure, which includes th
 -   [Documents in WPF](/dotnet/framework/wpf/advanced/documents-in-wpf)  
 
 ## See Also  
-[Create Modern Desktop Applications with Windows Presentation Foundation](../designers/create-modern-desktop-applications-with-windows-presentation-foundation.md)
+[Create Modern Desktop Applications with Windows Presentation Foundation](../designers/create-modern-desktop-applications-with-windows-presentation-foundation.md)

docs/ide/synchronized-settings-in-visual-studio.md

@@ -50,7 +50,7 @@ By default, the following settings are synchronized.
 
 ## Turn off synchronized settings on a particular computer
 
-Synchronized settings for Visual Studio are turned on by default. You can turn off synchronized settings on a computer by going to the **Tools | Options | Environment | Synchronized Settings** page and unchecking the checkbox.  For example, if you decide not to synchronize Visual Studio's settings on Computer A, any setting changes made on Computer A do not appear on Computer B or Computer C. Computer B and C will continue to synchronize with each other, but not with Computer A.
+Synchronized settings for Visual Studio are turned on by default. You can turn off synchronized settings on a computer by going to the **Tools | Options | Environment | Accounts** page and unchecking the checkbox.  For example, if you decide not to synchronize Visual Studio's settings on Computer A, any setting changes made on Computer A do not appear on Computer B or Computer C. Computer B and C will continue to synchronize with each other, but not with Computer A.
 
 ## Synchronize settings across Visual Studio family products and editions
 

docs/msbuild/msbuild-conditions.md

@@ -31,7 +31,7 @@ ms.workload:
 |---------------|-----------------|  
 |'`stringA`' == '`stringB`'|Evaluates to `true` if `stringA` equals `stringB`.<br /><br /> For example:<br /><br /> `Condition="'$(CONFIG)'=='DEBUG'"`<br /><br /> Single quotes are not required for simple alphanumeric strings or boolean values. However, single quotes are required for empty values.|  
 |'`stringA`' != '`stringB`'|Evaluates to `true` if `stringA` is not equal to `stringB`.<br /><br /> For example:<br /><br /> `Condition="'$(CONFIG)'!='DEBUG'"`<br /><br /> Single quotes are not required for simple alphanumeric strings or boolean values. However, single quotes are required for empty values.|  
-|\<, >, \<=, >=|Evaluates the numeric values of the operands. Returns `true` if the relational evaluation is true. Operands must evaluate to a decimal or hexadecimal number. Hexadecimal numbers must begin with "0x". **Note:**  In XML, the characters `<` and `>` must be escaped. The symbol `<` is represented as `<`. The symbol `>` is represented as `>`.|  
+|\<, >, \<=, >=|Evaluates the numeric values of the operands. Returns `true` if the relational evaluation is true. Operands must evaluate to a decimal or hexadecimal number. Hexadecimal numbers must begin with "0x". **Note:**  In XML, the characters `<` and `>` must be escaped. The symbol `<` is represented as `&lt;`. The symbol `>` is represented as `&gt;`.|  
 |Exists('`stringA`')|Evaluates to `true` if a file or folder with the name `stringA` exists.<br /><br /> For example:<br /><br /> `Condition="!Exists('$(builtdir)')"`<br /><br /> Single quotes are not required for simple alphanumeric strings or boolean values. However, single quotes are required for empty values.|  
 |HasTrailingSlash('`stringA`')|Evaluates to `true` if the specified string contains either a trailing backward slash (\\) or forward slash (/) character.<br /><br /> For example:<br /><br /> `Condition="!HasTrailingSlash('$(OutputPath)')"`<br /><br /> Single quotes are not required for simple alphanumeric strings or boolean values. However, single quotes are required for empty values.|  
 |!|Evaluates to `true` if the operand evaluates to `false`.|  
@@ -43,4 +43,4 @@ ms.workload:
 ## See Also  
  [MSBuild Reference](../msbuild/msbuild-reference.md)   
  [Conditional Constructs](../msbuild/msbuild-conditional-constructs.md)   
- [Walkthrough: Creating an MSBuild Project File from Scratch](../msbuild/walkthrough-creating-an-msbuild-project-file-from-scratch.md)
+ [Walkthrough: Creating an MSBuild Project File from Scratch](../msbuild/walkthrough-creating-an-msbuild-project-file-from-scratch.md)

docs/test/supported-configurations-and-platforms-for-coded-ui-tests-and-action-recordings.md

@@ -46,7 +46,7 @@ The supported configurations and platforms for coded UI tests for Visual Studio
 |Windows Phone Apps|Only WinRT-XAML based Phone apps are supported.|  
 |UWP apps|Only XAML-based UWP apps are supported.|  
 |Universal Windows Apps|Only XAML-based Universal Windows Apps on Phone and Desktop are supported.|  
-|Edge|In Visual Studio 2015 Update 2 and later by using the [Coded UI Cross Browser Testing extension](https://visualstudiogallery.msdn.microsoft.com/11cfc881-f8c9-4f96-b303-a2780156628d)|  
+|Edge|Recording of action steps or using the builder to view object properties is not supported. Tests can be played back on the Edge browser, using Visual Studio 2015 Update 2 and later versions by using the [Coded UI Cross Browser Testing extension](https://visualstudiogallery.msdn.microsoft.com/11cfc881-f8c9-4f96-b303-a2780156628d)|  
 |Internet Explorer 8<br /><br /> Internet Explorer 9<br /><br /> Internet Explorer 10 **Important:**  Internet Explorer 10 is only supported on the desktop. <br /><br /> Internet Explorer 11 **Important:**  Internet Explorer 11 is only supported on the desktop.|Fully supported.<br /><br /> -   **Support for HTML5 in Internet Explorer 9 and Internet Explorer 10:** Coded UI tests support record, playback, and validation of the HTML5 controls: Audio, Video, ProgressBar and Slider. For more information, see [Using HTML5 Controls in Coded UI Tests](../test/using-html5-controls-in-coded-ui-tests.md). **Warning:**      If you create a coded UI tests in Internet Explorer 10, it might not run using Internet Explorer 9 or Internet Explorer 8. This is because Internet Explorer 10 includes HTML5 controls such as Audio, Video, ProgressBar, and Slider. These HTML5 controls are not recognized by Internet Explorer 9, or Internet Explorer 8. Likewise, your coded UI test using Internet Explorer 9 might include some HTML5 controls that also will not be recognized by Internet Explorer 8.<br />-   **Support for Internet Explorer 10 Spell Checking:** Internet Explorer 10 includes spell checking capabilities for all text boxes. This allows you to choose from a list of suggested corrections. Coded UI Test will ignore user actions like selecting an alternative spelling suggestion. Only the final text typed into the text box will be recorded.<br />     The following actions are recorded for coded UI test that use the spell checking control: Add to Dictionary, Copy, Select All, Add To Dictionary, and Ignore.<br />-   **Support for 64-bit Internet Explorer running under Windows 8:** Previously, 64-bit versions of Internet Explorer were not supported for recording and playback. With [!INCLUDE[win8](../debugger/includes/win8_md.md)] and [!INCLUDE[vs_dev11_long](../data-tools/includes/vs_dev11_long_md.md)], coded UI tests have been enabled for 64-bit versions of Internet Explorer. **Warning:**      64-bit support for Internet Explorer applies only when you are running [!INCLUDE[win8](../debugger/includes/win8_md.md)] or later.<br />-   **Support for Pinned Sites in Internet Explorer 9:** In Internet Explorer 9, pinned sites were introduced. With Pinned Sites, you can get to your favorite sites directly from the Windows taskbar—without having to open Internet Explorer first. Coded UI tests can now generate intent-aware actions on pinned sites. For more information about pinned sites, see [Pinned Sites](http://go.microsoft.com/fwlink/?LinkId=220037).<br />-   **Support for Internet Explorer 9 Semantic Tags:** Internet Explorer 9 introduced the following semantic tags: section, nav, article, aside, hgroup, header, footer, figure, figcaption and mark. Coded UI tests ignore all of these semantic tags while recording. You can add assertions on these tags using the Coded UI Test Builder. You can use the navigation dial in the Coded UI Test Builder to navigate to any of these elements and view their properties.<br />-   **Seamless Handling of White Space Characters between Versions of Internet Explorer:** There are differences in the handling of white space characters between Internet Explorer 8, Internet Explorer 9, and Internet Explorer 10. Coded UI Test handles these differences seamlessly. Therefore, a coded UI test created in Internet Explorer 8 for example, will play back successfully in Internet Explorer 9 and Internet Explorer 10.<br />-   **The Notification Area of Internet Explorer Are Now Recorded With the "Continue on Error" Attribute Set:** All actions on the Notification Area of Internet Explorer are now recorded with the "Continue on Error" attribute set. If the notification bar does not appear during playback, the actions on it will be ignored and coded UI test will continue with the next action.|  
 |Windows Forms and WPF third party controls|Fully supported.<br /><br /> To enable third party controls in Windows Forms and WPF applications, you must add references and code. For more information, see [Enable Coded UI Testing of Your Controls](../test/enable-coded-ui-testing-of-your-controls.md).|  
 |Internet Explorer 6<br /><br /> Internet Explorer 7|Not supported.|