Merge remote-tracking branch 'MicrosoftDocs/master'

Author: timeyoutakeit

.openpublishing.redirection.json

@@ -2020,11 +2020,61 @@
             "redirect_url": "/visualstudio/test/run-unit-tests-with-test-explorer",
             "redirect_document_id": false
         },
+        {
+            "source_path": "docs/test/sample-coded-ui-test-extension-for-excel.md",
+            "redirect_url": "/visualstudio/test/extending-coded-ui-tests-and-action-recordings-to-support-microsoft-excel",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "docs/test/sample-excel-add-in-for-coded-ui-testing.md",
+            "redirect_url": "/visualstudio/test/extending-coded-ui-tests-and-action-recordings-to-support-microsoft-excel",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "docs/test/sample-excel-communicator-interface.md",
+            "redirect_url": "/visualstudio/test/extending-coded-ui-tests-and-action-recordings-to-support-microsoft-excel",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "docs/test/sample-excel-extension-actionfilter-class.md",
+            "redirect_url": "/visualstudio/test/extending-coded-ui-tests-and-action-recordings-to-support-microsoft-excel",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "docs/test/sample-excel-extension-element-classes.md",
+            "redirect_url": "/visualstudio/test/extending-coded-ui-tests-and-action-recordings-to-support-microsoft-excel",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "docs/test/sample-excel-extension-extensionpackage-class.md",
+            "redirect_url": "/visualstudio/test/extending-coded-ui-tests-and-action-recordings-to-support-microsoft-excel",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "docs/test/sample-excel-extension-propertyprovider-class.md",
+            "redirect_url": "/visualstudio/test/extending-coded-ui-tests-and-action-recordings-to-support-microsoft-excel",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "docs/test/sample-excel-extension-technologymanager-class.md",
+            "redirect_url": "/visualstudio/test/extending-coded-ui-tests-and-action-recordings-to-support-microsoft-excel",
+            "redirect_document_id": false
+        },
         {
             "source_path": "docs/test/testing-store-apps-with-visual-studio.md",
             "redirect_url": "/visualstudio/test/create-and-run-unit-tests-for-a-store-app-in-visual-studio/",
             "redirect_document_id": false
         },
+        {
+            "source_path": "docs/test/test-windows-phone-8-1-apps-with-coded-ui-tests.md",
+            "redirect_url": "/visualstudio/test/test-uwp-app-with-coded-ui-test",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "docs/test/test-windows-store-8-1-apps-with-coded-ui-tests.md",
+            "redirect_url": "/visualstudio/test/test-uwp-app-with-coded-ui-test",
+            "redirect_document_id": false
+        },
         {
             "source_path": "docs/test/troubleshooting-code-analysis-issues.md",
             "redirect_url": "/visualstudio/code-quality/analyzing-application-quality-by-using-code-analysis-tools",

docs/debugger/how-to-set-debug-and-release-configurations.md

@@ -55,7 +55,7 @@ You can change the build configuration from the **Build** menu, from the toolbar
 
      This toolbar is not available in Express editions. You can use the **Build Solution F6** and **Start Debugging F5** menu items to choose the configuration.
 
-## <a name="BKMK_symbols_release"></a>Generate symbol (.pbd) files for a build
+## <a name="BKMK_symbols_release"></a>Generate symbol (.pdb) files for a build
 
 For most project types, the .pdb files are generated by default for both debug and release builds, but the default settings are different depending on your specific project type and the version of Visual Studio. You can configure whether the compiler generates .pdb files and what kind of debug information to include.
 
@@ -112,4 +112,4 @@ For detailed information on project settings for debug configurations in C#, see
  [Project Settings for a C++ Debug Configuration](../debugger/project-settings-for-a-cpp-debug-configuration.md)   
  [Project Settings for  C# Debug Configurations](../debugger/project-settings-for-csharp-debug-configurations.md)   
  [Project Settings for a Visual Basic Debug Configuration](../debugger/project-settings-for-a-visual-basic-debug-configuration.md)   
- [How to: Create and Edit Configurations](../ide/how-to-create-and-edit-configurations.md)
+ [How to: Create and Edit Configurations](../ide/how-to-create-and-edit-configurations.md)

docs/install/visual-studio-administrator-guide.md

@@ -21,7 +21,7 @@ ms.workload:
 
 In enterprise environments, it's common for system administrators to deploy installations to end-users from a network share or by using systems management software. We've designed the Visual Studio setup engine to support enterprise deployment, allowing system administrators the ability to create a network install location, to pre-configure installation defaults, to deploy product keys during the installation process, and to manage product updates after a successful rollout. This administrator guide provides scenario-based guidance for enterprise deployment in networked environments.
 
-## Deploying Visual Studio 2017 in an enterprise environment
+## Deploy Visual Studio 2017 in an enterprise environment
 
 You can deploy Visual Studio 2017 to client workstations as long as each target computer meets the [minimum installation requirements](https://www.visualstudio.com/en-us/productinfo/vs2017-system-requirements-vs). Whether you're deploying through software like System Center or through a batch file, you'll typically want to go through the following steps:
 
@@ -44,7 +44,7 @@ You can deploy Visual Studio 2017 to client workstations as long as each target
 > [!IMPORTANT]
 > Note that installations from a network share will "remember" the source location they came from. This means that a repair of a client machine might need to return to the network share that the client originally installed from. Choose your network location carefully so that it aligns to the lifetime that you expect to have Visual Studio 2017 clients running in your organization.
 
-## Visual Studio tools
+## Use Visual Studio tools
 
 We have several tools available to help you [detect and manage installed Visual Studio instances](tools-for-managing-visual-studio-instances.md) on client machines.
 

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

@@ -5,7 +5,7 @@ keywords:
 author: TerryGLee
 ms.author: tglee
 manager: douge
-ms.date: 05/21/2018
+ms.date: 05/31/2018
 ms.topic: reference
 helpviewer_keywords:
 ms.prod: visual-studio-dev15
@@ -19,6 +19,7 @@ The following table lists the build numbers and release dates for Visual Studio
 
 | **Version**| **Channel** | **Release date** | **Build version** |
 | ---------------------- | ----------- | ---------------- | ----------------- |
+| 15.8.0 Preview 2.0 | Preview | May 31, 2018 | 15.8.27729.1 |
 | 15.7.2 | Release | May 21, 2018 | 15.7.27703.2018 |
 | 15.8.0 Preview 1.1 | Preview | May 8, 2018 | 15.8.27705.2000 |
 | 15.7.1 | Release | May 8, 2018 | 15.7.27703.2000 |

docs/python/learn-django-in-visual-studio-step-06-polls-django-web-project-template.md

@@ -249,7 +249,7 @@ urlpatterns = [
 ]
 ```
 
-If you're not familiar with the more complex regular expressions used here, you can paste the expression into [regex101.com](https://regex101.com/) for an explanation in plain language. (You'll need to escape the forward slashes `/` by adding a back slash, `\`h before them; escaping isn't necessary in Python because of the `r` prefix on the string, meaning "raw").
+If you're not familiar with the more complex regular expressions used here, you can paste the expression into [regex101.com](https://regex101.com/) for an explanation in plain language. (You'll need to escape the forward slashes `/` by adding a back slash, `\` before them; escaping isn't necessary in Python because of the `r` prefix on the string, meaning "raw").
 
 In Django, the syntax `?P<name>pattern` creates a group named `name`, which gets passed as arguments to views in the order they appear. In the code shown earlier, `PollsDetailView` and `PollsResultsView` receive an argument named `pk` and `app.views.vote` receives an argument named `poll_id`.
 

docs/sharepoint/additional-information-for-sharepoint-errors.md

@@ -22,10 +22,10 @@ manager: douge
 ms.workload: 
   - "office"
 ---
-# Additional Information for SharePoint Errors
+# Additional information for SharePoint errors
   You can find assistance in troubleshooting [!INCLUDE[vsprvs](../sharepoint/includes/vsprvs-md.md)] SharePoint tools errors and warnings in troubleshooting topics and the Microsoft Developer Network (MSDN) public forums.  
 
-## Troubleshooting Errors and Issues  
+## Troubleshoot errors and issues
  For assistance with some common errors and other issues in [!INCLUDE[vsprvs](../sharepoint/includes/vsprvs-md.md)] SharePoint tools, see the following topics:  
 
 -   [Troubleshooting SharePoint Solutions](../sharepoint/troubleshooting-sharepoint-solutions.md)  
@@ -34,7 +34,7 @@ ms.workload:
 
 -   [Troubleshooting SharePoint Packaging and Deployment](../sharepoint/troubleshooting-sharepoint-packaging-and-deployment.md)  
 
-## Other Resources  
+## Other resources
  The following table lists the [!INCLUDE[vsprvs](../sharepoint/includes/vsprvs-md.md)] SharePoint tools forums and other resources available on MSDN.  
 
 |Term|Definition|  
@@ -45,7 +45,7 @@ ms.workload:
 
  If you still cannot find  the answers that you need, you can access online support options, such as contacting Microsoft Product Support Services or searching KnowledgeBase articles. For more information, see the [Microsoft Help and Support](http://go.microsoft.com/fwlink/?LinkID=155371) page.  
 
-## See Also  
+## See also
  [Building and Debugging SharePoint Solutions](../sharepoint/building-and-debugging-sharepoint-solutions.md)  
 
-  
+ 

docs/sharepoint/api-reference-sharepoint-tools-extensibility.md

@@ -16,10 +16,10 @@ manager: douge
 ms.workload: 
   - "office"
 ---
-# API Reference (SharePoint Tools Extensibility)
+# API reference (SharePoint tools extensibility)
   This section contains API reference documentation for extending the SharePoint tools in Visual Studio.  
 
-## In This Section  
+## In this section
  <xref:Microsoft.VisualStudio.SharePoint>  
  Contains types that you use to extend the SharePoint project system. For example, you can extend the built-in SharePoint projects and project items, or you can create your own project items.  
 
@@ -53,12 +53,11 @@ ms.workload:
  <xref:Microsoft.VisualStudio.SharePoint.Validation>  
  Contains types that you use to customize the feature and package validation behavior for a SharePoint project.  
 
-## See Also  
+## See also
  [Reference &#40;SharePoint Tools Extensibility&#41;](../sharepoint/reference-sharepoint-tools-extensibility.md)   
  [Overview of the Programming Model of SharePoint Tools Extensions](../sharepoint/overview-of-the-programming-model-of-sharepoint-tools-extensions.md)   
  [Extending the SharePoint Project System](../sharepoint/extending-the-sharepoint-project-system.md)   
  [Extending the SharePoint Connections Node in Server Explorer](../sharepoint/extending-the-sharepoint-connections-node-in-server-explorer.md)   
  [Extending SharePoint Packaging and Deployment](../sharepoint/extending-sharepoint-packaging-and-deployment.md)   
  [Calling into the SharePoint Object Models](../sharepoint/calling-into-the-sharepoint-object-models.md)  
 
-  

docs/sharepoint/associating-custom-data-with-sharepoint-tools-extensions.md

@@ -20,7 +20,7 @@ manager: douge
 ms.workload: 
   - "office"
 ---
-# Associating Custom Data with SharePoint Tools Extensions
+# Associating custom data with SharePoint tools extensions
   You can add custom data to certain objects in SharePoint tools extensions. This is useful when you have data in one part of your extension that you want to access later from other code in your extension. Instead of implementing a custom way to store and access data, you can associate the data with an object in your extension and then retrieve the data from the same object later.  
 
  Adding custom data to objects is also useful when you want to preserve data that is relevant to a specific item in Visual Studio. SharePoint tools extensions are loaded just once in Visual Studio, so your extension might work with several different items (such as projects, project items, or **Server Explorer** nodes) at any time. If you have custom data that is relevant only to a specific item, you can add the data to the object that represents that item.  
@@ -29,7 +29,7 @@ ms.workload:
 
  In extensions of the SharePoint project system, you can also save string data that persists after an extension is unloaded. For more information, see [Saving Data in Extensions of the SharePoint Project System](../sharepoint/saving-data-in-extensions-of-the-sharepoint-project-system.md).  
 
-## Objects that Can Contain Custom Data  
+## Objects that can contain custom data
  You can add custom data to any object in the SharePoint tools object model that implements the <xref:Microsoft.VisualStudio.SharePoint.IAnnotatedObject> interface. This interface defines just one property, <xref:Microsoft.VisualStudio.SharePoint.IAnnotatedObject.Annotations%2A>, which is a collection of custom data objects. The following types implement <xref:Microsoft.VisualStudio.SharePoint.IAnnotatedObject>:  
 
 -   <xref:Microsoft.VisualStudio.SharePoint.IMappedFolder>  
@@ -62,7 +62,7 @@ ms.workload:
 
 -   <xref:Microsoft.VisualStudio.SharePoint.Explorer.IExplorerNodeTypeDefinition>  
 
-## Adding and Retrieving Custom Data  
+## Add and retrieve custom data
  To add custom data to an object in a SharePoint tools extension, get the <xref:Microsoft.VisualStudio.SharePoint.IAnnotatedObject.Annotations%2A> property of the object you want to add the data to, and then use the <xref:Microsoft.VisualStudio.SharePoint.IAnnotationDictionary.Add%2A> method to add the data to the object.  
 
  To retrieve custom data from an object in a SharePoint tools extension, get the <xref:Microsoft.VisualStudio.SharePoint.IAnnotatedObject.Annotations%2A> property of the object and then use one of the following methods:  
@@ -76,10 +76,10 @@ ms.workload:
  [!code-vb[SPExtensibility.ProjectItemExtension.MenuAndProperty#13](../sharepoint/codesnippet/VisualBasic/projectitemmenuandproperty/extension/projectitemtypeproperty.vb#13)]
  [!code-csharp[SPExtensibility.ProjectItemExtension.MenuAndProperty#13](../sharepoint/codesnippet/CSharp/projectitemmenuandproperty/extension/projectitemtypeproperty.cs#13)]  
 
-## See Also  
+## See also
  [Programming Concepts and Features for SharePoint Tools Extensions](../sharepoint/programming-concepts-and-features-for-sharepoint-tools-extensions.md)   
  [Walkthrough: Creating a Custom Action Project Item with an Item Template, Part 1](../sharepoint/walkthrough-creating-a-custom-action-project-item-with-an-item-template-part-1.md)   
  [Walkthrough: Extending Server Explorer to Display Web Parts](../sharepoint/walkthrough-extending-server-explorer-to-display-web-parts.md)   
  [How to: Add a Property to SharePoint Projects](../sharepoint/how-to-add-a-property-to-sharepoint-projects.md)   
  [How to: Add a Property to a Custom SharePoint Project Item Type](../sharepoint/how-to-add-a-property-to-a-custom-sharepoint-project-item-type.md   
-  
+ 

docs/sharepoint/bdc-model-design-tools-overview.md

@@ -29,12 +29,12 @@ manager: douge
 ms.workload: 
   - "office"
 ---
-# BDC Model Design Tools Overview
+# BDC model design tools overview
   You can design a Business Data Connectivity (BDC) model by using the BDC Designer, the **BDC Method Details** window, and the **BDC Explorer**.  
 
  The **BDC Explorer** enables you to browse the model, search the model, and define type descriptors.  
 
-## BDC Designer  
+## BDC Designer
  The BDC Designer enables you to define the entities in your model and to visually arrange their relationships with one another. Use the BDC Designer to accomplish the following tasks:  
 
 -   Add entities to the model.  
@@ -45,7 +45,7 @@ ms.workload:
 
  To open the BDC Designer, double-click the model file in your project, or open the shortcut menu for the model file and then choose **Open**. Add an entity to the model by dragging or copying an **Entity** from the **Toolbox** onto the designer. To create an association between two entities, choose the **Association** control in the **Toolbox**, choose the first entity, and then choose the second entity.  
 
-## BDC Method Details Window  
+## BDC method details window
  Use the **BDC Method Details** window to define the parameters, instances, and filter descriptors of a method.  
 
  You can quickly generate Finder, Specific Finder, Creator, Updater, and Deleter methods in the **BDC Method Details** window. When you generate these methods, Visual Studio adds metadata, such as parameters, instances, and type descriptors, to the method. You can modify this metadata to satisfy your specific scenario.  
@@ -56,23 +56,23 @@ ms.workload:
 
  Expand or collapse nodes in the **BDC Method Details** window to define parameters, instances, and filter descriptors. Use the **BDC Explorer** to define type descriptors.  
 
-## BDC Explorer  
+## BDC Explorer
  The **BDC Explorer** displays the elements that make up the model. To open the **BDC Explorer**, on the menu bar, choose **View**, **Other Windows**, **BDC Explorer**. To browse the model, expand nodes in the **BDC Explorer**. Each node represents an element in the XML of the model file.  
 
  As you choose nodes in the **BDC Explorer**, the properties of each node that you choose appear in the **Properties** window. Many of these properties correspond to attributes in the model file. You can search the model by using the search box at the top of the **BDC Explorer**.  
 
 > [!NOTE]  
 >  The **BDC Explorer** does not display identifiers, custom properties, localized strings, association groups, actions, filter descriptors, action control lists, and the default parameter values.  
   
-### Defining Type Descriptors  
+### Define type descriptors
  Use the **BDC Explorer** to define type descriptors. The BDC Explorer enables you to define a type descriptor one time and then reuse that type descriptor elsewhere in your model. To accomplish this, copy a type descriptor and paste it onto any other parameter or type descriptor.  
 
 > [!NOTE]  
 >  Changes to an original type descriptor do not affect the copies of that type descriptor.  
   
  For more information, see [How to: Define the Type Descriptor of a Parameter](../sharepoint/how-to-define-the-type-descriptor-of-a-parameter.md).  
 
-## See Also  
+## See also
  [How to: Create a BDC Model](../sharepoint/how-to-create-a-bdc-model.md)   
  [How to: Add an Entity to a Model](../sharepoint/how-to-add-an-entity-to-a-model.md)   
  [How to: Add a Finder Method](../sharepoint/how-to-add-a-finder-method.md)   
@@ -86,4 +86,4 @@ ms.workload:
  [Creating a Business Data Connectivity Model](../sharepoint/creating-a-business-data-connectivity-model.md)   
  [Designing a Business Data Connectivity Model](../sharepoint/designing-a-business-data-connectivity-model.md)  
 
-  
+