Merge pull request #1579 from MicrosoftDocs/master

3/9 AM Publish

Author: Taojunshen

docs/docfx.json

@@ -51,7 +51,7 @@
       "uhfHeaderId": "MSDocsHeader-VisualStudio"
     },
     "template": [],
-    "xref": ["missingapi.yml", "../dotnet-xref/_zip/dotnet.zip", "vs.110.zip", "vs.140.zip", "office15.zip"],
+    "xref": ["missingapi.yml", "../dotnet-xref/_zip/dotnet.zip"],
     "dest": "vsdocsdocs"
   }
 }

docs/extensibility/how-to-diagnose-ui-delays-caused-by-extensions.md

@@ -153,5 +153,7 @@ PerfView has detailed guidance under the Help menu that you can use to identify
 * [https://aka.ms/vsthreading](https://aka.ms/vsthreading)
 * [https://aka.ms/vsthreadingcookbook](https://aka.ms/vsthreadingcookbook)
 
+You can also use the new Visual Studio static analyzers for extensions (NuGet package [here](https://www.nuget.org/packages/microsoft.visualstudio.sdk.analyzers)), that provide guidance on best practices for writing efficient extensions. See a list of [VS SDK analyzers](https://github.com/Microsoft/VSSDK-Analyzers/blob/master/doc/index.md) and [threading analyzers](https://github.com/Microsoft/vs-threading/blob/master/doc/analyzers/index.md).
+
 > [!NOTE]
 > If you are unable to address the unresponsiveness due to dependencies you do not have control over (e.g. if your extension has to call synchronous VS services on the UI thread), we would like to know about it. If you are a member of our Visual Studio Partner program, you can contact us by submitting a developer support request. Otherwise, use the 'Report a Problem' tool to submit your feedback and include `"Extension UI Delay Notifications"` in the title. Please also include a detailed description of your analysis.

docs/install/visual-studio-build-numbers-and-release-dates.md

@@ -5,7 +5,7 @@ keywords:
 author: TerryGLee
 ms.author: tglee
 manager: ghogen
-ms.date: 03/05/2018
+ms.date: 03/08/2018
 ms.topic: article
 helpviewer_keywords:
 ms.technology:
@@ -21,6 +21,8 @@ The following table lists the build numbers and release dates for Visual Studio
 
 | **Version**| **Channel** | **Release date** | **Build version** |
 | ---------------------- | ----------- | ---------------- | ----------------- |
+| 15.6.1 | Release | March 8, 2018 | 15.6.27428.2002 |
+| 15.6.1 Preview 1.0 | Preview | March 8, 2018 | 15.6.27428.2002 |
 | 15.6.0 | Release | March 5, 2018 | 15.6.27428.1 |
 | 15.6.0 Preview 7.0 | Preview | March 2, 2018 | 15.6.27428.1 |
 | 15.6.0 Preview 6.0 | Preview | February 23, 2018 | 15.6.27421.1 |

docs/office15.zip

@@ -44,29 +44,29 @@ For details on creating a firewall rule for an Azure VM, see [Opening ports to a
 
 1. On the remote computer, create a Python file called `guessing-game.py` with the following code:
 
-  ```python
-  import random
-
-  guesses_made = 0
-  name = input('Hello! What is your name?\n')
-  number = random.randint(1, 20)
-  print('Well, {0}, I am thinking of a number between 1 and 20.'.format(name))
-
-  while guesses_made < 6:
-      guess = int(input('Take a guess: '))
-      guesses_made += 1
-      if guess < number:
-          print('Your guess is too low.')
-      if guess > number:
-          print('Your guess is too high.')
-      if guess == number:
-          break
-  if guess == number:
-      print('Good job, {0}! You guessed my number in {1} guesses!'.format(name, guesses_made))
-  else:
-      print('Nope. The number I was thinking of was {0}'.format(number))
-  ```
- 
+    ```python
+    import random
+
+    guesses_made = 0
+    name = input('Hello! What is your name?\n')
+    number = random.randint(1, 20)
+    print('Well, {0}, I am thinking of a number between 1 and 20.'.format(name))
+
+    while guesses_made < 6:
+        guess = int(input('Take a guess: '))
+        guesses_made += 1
+        if guess < number:
+            print('Your guess is too low.')
+        if guess > number:
+            print('Your guess is too high.')
+        if guess == number:
+            break
+    if guess == number:
+        print('Good job, {0}! You guessed my number in {1} guesses!'.format(name, guesses_made))
+    else:
+        print('Nope. The number I was thinking of was {0}'.format(number))
+    ```
+
 1. Install the `ptvsd` package into your environment using `pip3 install ptvsd`. (Note: it's a good idea to record the version of ptvsd that's installed in case you need it for troubleshooting; the [ptvsd listing](https://pypi.python.org/pypi/ptvsd) also shows available versions.)
 
 1. Enable remote debugging by adding the code below at the earliest possible point in `guessing-game.py`, before other code. (Though not a strict requirement, it's impossible to debug any background threads spawned before the `enable_attach` function is called.)

docs/python/debugging-python-code-on-remote-linux-machines.md

@@ -2,7 +2,7 @@
 title: Quickstart - Create a Python project in Visual Studio using a template | Microsoft Docs
 description: Get started quickly using Python by creating a Visual Studio project using one of the built-in templates.
 ms.custom:
-ms.date: 09/25/2017
+ms.date: 03/08/2018
 ms.reviewer:
 ms.suite:
 ms.technology: 
@@ -62,22 +62,22 @@ Once you've [installed Python support in Visual Studio 2017](installing-python-s
             output += "%04d" % (carry + (total / scale))
             carry = total % scale
 
-        return output;
+        return output
 
     def test_py():
-        digits = 1000;
+        digits = 1000
 
         start = perf_counter()
-        output = pi_digits_Python(digits);
-        elapsed = perf_counter() - start;
+        output = pi_digits_Python(digits)
+        elapsed = perf_counter() - start
 
         print("PI to " + str(digits) + " digits in " + str(int(elapsed * 10000)/10000) + " seconds:")
 
         ## replace inserts the decimal point
         print(output.replace("3", "3.", 1))
 
     if __name__ == "__main__":
-        test_py();
+        test_py()
     ```
 
 1. Run the program by pressing Ctrl+F5 or selecting **Debug > Start Without Debugging** on the menu. The results are displayed in a console window.

docs/python/media/vs-getting-started-python-11-interactive1.png

@@ -72,7 +72,7 @@ Although Solution Explorer is where you manage project files, the *editor* windo
 
     ```python
     import sys
-    from math import sin, cos, radians
+    from math import cos, radians
     ```
 
     > [!Tip]

docs/python/media/vs-getting-started-python-11-interactive1b.png

@@ -2,7 +2,7 @@
 title: Working with Python in Visual Studio, Step 4, Debugging | Microsoft Docs
 description: Step 4 of a core tutorial for working with Python within Visual Studio, covering how to run Python code in the debugger.
 ms.custom:
-ms.date: 01/16/2018
+ms.date: 03/08/2018
 ms.reviewer:
 ms.suite:
 ms.technology: 
@@ -28,15 +28,14 @@ In addition to managing projects, providing a rich editing experience, and the i
 1. Replace the code in the `PythonApplication1.py` file with the following. This variation of the code expands `make_dot_string` so that you can examine its discrete steps in the debugger. It also places the `for` loop into a `main` function and runs it explicitly by calling that function:
 
     ```python
-    import sys
-    from math import sin, cos, radians
+    from math import cos, radians
 
     # Create a string with spaces proportional to a cosine of x in degrees
     def make_dot_string(x):
         rad = radians(x)                             # cos works with radians
         numspaces = int(20 * cos(radians(x)) + 20)   # scale to 0-40 spaces
-        str = ' ' * numspaces + 'o'                  # place 'o' after the spaces
-        return str
+        st = ' ' * numspaces + 'o'                   # place 'o' after the spaces
+        return st
 
     def main():
         for i in range(0, 1800, 12):

docs/python/media/vs-getting-started-python-19-debugging2.png

@@ -52,9 +52,9 @@ The Python developer community has produced thousands of useful packages that yo
 1. Create a new project with **File > New > Project**, selecting the "Python Application" template. In the code file that appears, paste the following code, which creates a cosine wave like the previous tutorial steps, only this time plotted graphically:
 
     ```python
+    from math import radians
     import numpy as np     # installed with matplotlib
     import matplotlib.pyplot as plt
-    from math import radians
 
     def main():
         x = np.arange(0, radians(1800), radians(12))

docs/python/media/vs-getting-started-python-19-debugging2b.png

@@ -39,16 +39,16 @@ By convention, Visual Studio identifies tests are as methods whose names start w
 
 1. This action creates a `test1.py` file with code that imports the standard `unittest` module, derives a test class from `unittest.TestCase`, and invokes `unittest.main()` if you run the script directly:
 
-  ```python
-  import unittest
+    ```python
+    import unittest
 
-  class Test_test1(unittest.TestCase):
-      def test_A(self):
-          self.fail("Not implemented")
+    class Test_test1(unittest.TestCase):
+        def test_A(self):
+            self.fail("Not implemented")
 
-  if __name__ == '__main__':
-      unittest.main()
-  ```
+    if __name__ == '__main__':
+        unittest.main()
+    ```
 
 1. Save the file if necessary, then open Test Explorer with the **Test > Windows > Test Explorer** menu command.
 

docs/python/quickstart-02-python-in-visual-studio-project-from-template.md

@@ -52,7 +52,24 @@ Visual Studio Test Explorer can run any unit test framework that has developed a
 
 3.  In the **Category** list (labeled as **Showing**), expand the **Tools** node and then choose **Testing**.  
 
-4.  Choose a framework in the results list to navigate to a Visual Studio Marketplace page for the tool.  
-  
-## See Also  
- [Unit Test Your Code](../test/unit-test-your-code.md)
+4.  Choose a framework in the results list to navigate to a Visual Studio Marketplace page for the tool. 
+
+## Update to the latest test adapters
+
+Update to the latest stable test adapter to experience better test discovery and execution. For more information about updates to MSTest, NUnit, and xUnit test adapters, see the [Visual Studio blog](https://blogs.msdn.microsoft.com/visualstudio/2017/11/16/test-experience-improvements/).
+
+### To update to the latest stable test adapter version
+
+1. Open the Nuget Package Manager for your solution by navigating to **Tools > NuGet Package Manager > Manage NuGet Packages for Solution...**
+
+2. Click on the **Updates** tab and search for NUnit or xUnit test adapters that are installed.
+
+3. Select each test adapter, and then select the latest stable version in the drop down menu.
+
+4. Choose the **Install** button.
+
+![Upgrade Test Adapter](media/installadapter-upgrade.png)
+
+## See also
+
+- [Unit Test Your Code](../test/unit-test-your-code.md)

docs/python/tutorial-working-with-python-in-visual-studio-step-02-writing-code.md

@@ -59,10 +59,16 @@ manager: ghogen
 
 ### 8. How does sorting test results work in the hierarchy view?
 
-  The hierarchy view sorts tests alphabetically as opposed to by outcome. The other group by settings normally sort test results by outcome and then alphabetically. The different group by options are shown below for comparison. You can provide feedback about the design [in this GitHub issue](https://github.com/Microsoft/vstest/issues/1425).
+  The hierarchy view sorts tests alphabetically as opposed to by outcome. The other group by settings normally sort test results by outcome and then alphabetically. See the different group by options in the following image for comparison. You can provide feedback about the design [in this GitHub issue](https://github.com/Microsoft/vstest/issues/1425).
 
   ![SortingExamples](media/testex-sortingex.png)
 
+### 9. In the hierarchy view, there are passed, failed, skipped, and not run icons next to the Project, Namespace, and Class groupings. What do these icons mean?
+
+  The icons next to the Project, Namespace, and Class groupings reflect the state of the tests within that grouping. See the following table.
+
+  ![Test Explorer Hierarchy Icons](media/testex-hierarchyicons.png)
+
 ## Features
 
 ### How can I turn on feature flags to try out new testing features?

docs/python/tutorial-working-with-python-in-visual-studio-step-04-debugging.md

@@ -1,40 +1,36 @@
 ---
 title: "Activity Views (Legacy) | Microsoft Docs"
-ms.custom: ""
 ms.date: "11/04/2016"
-ms.reviewer: ""
-ms.suite: ""
-ms.tgt_pltfrm: ""
 ms.topic: "reference"
 helpviewer_keywords: 
   - "activities, activity views"
   - "views, activity"
   - "activity views"
 ms.assetid: 83dc68cd-2cb2-45c2-9a6e-10d82053171a
-caps.latest.revision: 5
-author: "ErikRe"
-ms.author: "erikre"
-manager: "erikre"
+author: gewarren
+ms.author: gewarren
+manager: ghogen
 ms.workload: 
   - "multiple"
 ---
 # Activity Views (Legacy)
-Many of the activities provided by [!INCLUDE[wf](../workflow-designer/includes/wf_md.md)], from which workflows are composed, have several design views available in the legacy [!INCLUDE[wfd1](../workflow-designer/includes/wfd1_md.md)]. When you drag an activity designer from the **Toolbox** onto the design surface, and thereafter whenever you select the activity, you can switch between the different design views by using either the **Workflow** menu or by right-clicking the selected activity. Also, when you move the pointer over the name of a selected activity, a drop-down set of tabs appears that you can use to switch between the different views.  
-  
- Every activity has at least one view; this is the default view shown when you drag an activity designer from the **Toolbox** onto the design surface. This activity default view is available as the **View [activity type]** option on the menus and tab, for example, **View Parallel**. Most of the activities have additional views and different activities can have different views. For example, the [TransactionScopeActivity](http://go.microsoft.com/fwlink?LinkID=65093) activity has the compensation view and the [EventHandlingScopeActivity](http://go.microsoft.com/fwlink?LinkID=65030) activity has an events view. Many of the activities that come with Windows Workflow Foundation have **View Cancel Handler** and **View Faults** design views to view the [CancellationHandlerActivity](http://go.microsoft.com/fwlink?LinkID=65050) and a [FaultHandlersActivity](http://go.microsoft.com/fwlink?LinkID=65055) associated with them.  
-  
- The following table lists the name and description of each view.  
-  
-|Menu/Tab Option|Description|  
-|----------------------|-----------------|  
-|**View [activity type]**|Select this menu or tab option to view the default graphical representation of the selected activity.|  
-|**View Cancel Handler**|Select this menu or tab option view to view the [CancellationHandlerActivity](http://go.microsoft.com/fwlink?LinkID=65050) associated with the selected activity.|  
-|**View Fault Handler**|Select this menu or tab option view to view the [FaultHandlersActivity](http://go.microsoft.com/fwlink?LinkID=65055) associated with the selected activity.|  
-|**View Compensation Handler**|Select this menu or tab option view to view the [CompensationHandlerActivity](http://go.microsoft.com/fwlink?LinkID=65053) associated with the selected [TransactionScopeActivity](http://go.microsoft.com/fwlink?LinkID=65093).|  
-|**View Events Handler**|Select this menu or tab option view to view the [EventHandlersActivity](http://go.microsoft.com/fwlink?LinkID=65018) associated with the selected the [EventHandlingScopeActivity](http://go.microsoft.com/fwlink?LinkID=65030).|  
-  
- For information about similar views, see [Sequential Workflow Views (Legacy)](../workflow-designer/sequential-workflow-views-legacy.md).  
-  
-## See Also  
- [Legacy Workflow Activities](../workflow-designer/legacy-workflow-activities.md)   
- [Sequential Workflow Views (Legacy)](../workflow-designer/sequential-workflow-views-legacy.md)
+Many of the activities provided by [!INCLUDE[wf](../workflow-designer/includes/wf_md.md)], from which workflows are composed, have several design views available in the legacy Windows Workflow Designer. When you drag an activity designer from the **Toolbox** onto the design surface, and thereafter whenever you select the activity, you can switch between the different design views by using either the **Workflow** menu or by right-clicking the selected activity. Also, when you move the pointer over the name of a selected activity, a drop-down set of tabs appears that you can use to switch between the different views.
+
+ Every activity has at least one view; this is the default view shown when you drag an activity designer from the **Toolbox** onto the design surface. This activity default view is available as the **View [activity type]** option on the menus and tab, for example, **View Parallel**. Most of the activities have additional views and different activities can have different views. For example, the [TransactionScopeActivity](http://go.microsoft.com/fwlink?LinkID=65093) activity has the compensation view and the [EventHandlingScopeActivity](http://go.microsoft.com/fwlink?LinkID=65030) activity has an events view. Many of the activities that come with Windows Workflow Foundation have **View Cancel Handler** and **View Faults** design views to view the [CancellationHandlerActivity](http://go.microsoft.com/fwlink?LinkID=65050) and a [FaultHandlersActivity](http://go.microsoft.com/fwlink?LinkID=65055) associated with them.
+
+ The following table lists the name and description of each view.
+
+|Menu/Tab Option|Description|
+|----------------------|-----------------|
+|**View [activity type]**|Select this menu or tab option to view the default graphical representation of the selected activity.|
+|**View Cancel Handler**|Select this menu or tab option view to view the [CancellationHandlerActivity](http://go.microsoft.com/fwlink?LinkID=65050) associated with the selected activity.|
+|**View Fault Handler**|Select this menu or tab option view to view the [FaultHandlersActivity](http://go.microsoft.com/fwlink?LinkID=65055) associated with the selected activity.|
+|**View Compensation Handler**|Select this menu or tab option view to view the [CompensationHandlerActivity](http://go.microsoft.com/fwlink?LinkID=65053) associated with the selected [TransactionScopeActivity](http://go.microsoft.com/fwlink?LinkID=65093).|
+|**View Events Handler**|Select this menu or tab option view to view the [EventHandlersActivity](http://go.microsoft.com/fwlink?LinkID=65018) associated with the selected the [EventHandlingScopeActivity](http://go.microsoft.com/fwlink?LinkID=65030).|
+
+ For information about similar views, see [Sequential Workflow Views (Legacy)](../workflow-designer/sequential-workflow-views-legacy.md).
+
+## See also
+
+- [Legacy Workflow Activities](../workflow-designer/legacy-workflow-activities.md)
+- [Sequential Workflow Views (Legacy)](../workflow-designer/sequential-workflow-views-legacy.md)