Merge pull request #647 from MicrosoftDocs/FromPublicMaster

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

Author: Greg Van Liew

CONTRIBUTING.md

@@ -19,7 +19,7 @@ The content inside the **docs** folder is organized into sections that are organ
 
 You can skip this first step for small changes.
 
-**Step 2:** Fork the `Microsoft/visualstudio-docs` repo.
+**Step 2:** Fork the `MicrosoftDocs/visualstudio-docs` repo.
 
 **Step 3:** Create a `branch` for your article.
 
@@ -42,7 +42,7 @@ Be sure to follow the proper Markdown syntax. See the [style guide](./styleguide
           /media
               debugging-installed-app-package.png
 
-**Step 5:** Submit a Pull Request (PR) from your branch to `Microsoft/visualstudio-docs/master`.
+**Step 5:** Submit a Pull Request (PR) from your branch to `MicrosoftDocs/visualstudio-docs/master`.
 
 If your PR is addressing an existing issue, add the `Fixes #Issue_Number` keyword to the commit message or PR description, so the issue can be automatically closed when the PR is merged. For more information, see [Closing issues via commit messages](https://help.github.com/articles/closing-issues-via-commit-messages/).
 

docs/data-tools/add-code-to-datasets-in-n-tier-applications.md

@@ -39,7 +39,7 @@ You can extend the functionality of a dataset by creating a partial class file f
 
  The code that defines a dataset is generated every time changes are made to the dataset definition (in the typed dataset). This code is also generated when you make changes during the running of any wizard that modifies the configuration of a dataset. To prevent your code from being deleted during the regeneration of a dataset, add code to the dataset's partial class file.  
 
- By default, after you separate the dataset and `TableAdapter` code, the result is a discrete class file in each project. The original project has a filenamed *DatasetName*.Designer.vb (or *DatasetName*.Designer.cs) that contains the `TableAdapter` code. The project that's designated in the **Dataset Project** property has a file that's named *DatasetName*.DataSet.Designer.vb (or *DatasetName*.DataSet.Designer.cs).This file contains the dataset code.  
+ By default, after you separate the dataset and `TableAdapter` code, the result is a discrete class file in each project. The original project has a file named *DatasetName*.Designer.vb (or *DatasetName*.Designer.cs) that contains the `TableAdapter` code. The project that's designated in the **Dataset Project** property has a file that's named *DatasetName*.DataSet.Designer.vb (or *DatasetName*.DataSet.Designer.cs).This file contains the dataset code.  
 
 > [!NOTE]
 >  When you separate datasets and `TableAdapter`s (by setting the **DataSet Project** property), existing partial dataset classes in the project won't be moved automatically. Existing dataset partial classes must be moved manually to the dataset project.  
@@ -53,7 +53,7 @@ You can extend the functionality of a dataset by creating a partial class file f
 
 2.  Select the **.xsd** file to open the dataset.  
 
-3.  Right-click the data table to which you want to add code (the table name in the title bar), and thenselect**View Code**.  
+3.  Right-click the data table to which you want to add code (the table name in the title bar), and then select **View Code**.  
 
      A partial class is created and opens in the Code Editor.  
 

docs/data-tools/add-code-to-tableadapters-in-n-tier-applications.md

@@ -56,7 +56,7 @@ You can extend the functionality of a `TableAdapter` by creating a partial class
 
 2.  Double click the **.xsd** file to open the **Dataset Designer**.  
 
-3.  Right-click the `TableAdapter` that you want to add code to, and then select**View Code**.  
+3.  Right-click the `TableAdapter` that you want to add code to, and then select **View Code**.  
 
      A partial class is created and opens in the Code Editor.  
 

docs/data-tools/add-new-data-sources.md

@@ -64,7 +64,7 @@ In the context of .NET data tools in Visual Studio, the term *data source* refer
 ## Data source for a database or a database file  
 
 ### Dataset  
- To create a dataset as a data source, run the **Data Source Configuration Wizard** (**Project** > **Add New Data** Source) and choose the **Database** data-source type. Follow the prompts to specify a new or existing database connection, or a database file.  
+ To create a dataset as a data source, run the **Data Source Configuration Wizard** (**Project** > **Add New Data Source**) and choose the **Database** data-source type. Follow the prompts to specify a new or existing database connection, or a database file.  
 
 ### Entity classes  
  To create an Entity Framework model as a data source, first run the **Entity Data Model Wizard** to create the entity classes (**Project** > **Add New Item** > **ADO.NET Entity Data Model**).  

docs/data-tools/add-validation-to-an-n-tier-dataset.md

@@ -67,7 +67,7 @@ End Sub
 
 #### To add validation during changes to individual column values  
 
-1.  Open the dataset in The datasetby double-clicking the **.xsd** file in **Solution Explorer**. For more information, see [Walkthrough: Creating a Dataset in the Dataset Designer](walkthrough-creating-a-dataset-with-the-dataset-designer.md).  
+1.  Open the dataset in The dataset by double-clicking the **.xsd** file in **Solution Explorer**. For more information, see [Walkthrough: Creating a Dataset in the Dataset Designer](walkthrough-creating-a-dataset-with-the-dataset-designer.md).  
 
 2.  Double-click the column you want to validate. This action creates the <xref:System.Data.DataTable.ColumnChanging> event handler.  
 
@@ -76,7 +76,7 @@ End Sub
   
 3.  Add code to verify that `e.ProposedValue` contains data that meets the requirements of your application. If the proposed value is unacceptable, set the column to indicate that it contains an error.  
 
-     The following code example validates that the **Quantity** column contains more than 0. If**Quantity** is less than or equal to 0, the column is set to an error. The `Else` clause clears the error if**Quantity** is more than 0. The code in the column-changing event handler should resemble the following:  
+     The following code example validates that the **Quantity** column contains more than 0. If **Quantity** is less than or equal to 0, the column is set to an error. The `Else` clause clears the error if **Quantity** is more than 0. The code in the column-changing event handler should resemble the following:  
 
     ```vb#  
     If (e.Column.ColumnName = Me.QuantityColumn.ColumnName) Then  
@@ -117,7 +117,7 @@ End Sub
         }  
     ```  
   
-## Validatechanges to whole rows  
+## Validate changes to whole rows  
  Validate values in whole rows by handling the <xref:System.Data.DataTable.RowChanging> event. The <xref:System.Data.DataTable.RowChanging> event is raised when the values in all columns are committed. It is necessary to validate in the <xref:System.Data.DataTable.RowChanging> event when the value in one column relies on the value in another column. For example, consider OrderDate and RequiredDate in the Orders table in Northwind.  
   
  When orders are being entered, validation makes sure that an order is not entered with a RequiredDate that is on or before the OrderDate. In this example, the values for both the RequiredDate and OrderDate columns need to be compared, so validating an individual column change does not make sense.  
@@ -126,7 +126,7 @@ End Sub
   
 #### To add validation during changes to whole rows  
   
-1.  Open the dataset in The datasetby double-clicking the **.xsd** file in **Solution Explorer**. For more information, see [Walkthrough: Creating a Dataset in the Dataset Designer](walkthrough-creating-a-dataset-with-the-dataset-designer.md).  
+1.  Open the dataset in The dataset by double-clicking the **.xsd** file in **Solution Explorer**. For more information, see [Walkthrough: Creating a Dataset in the Dataset Designer](walkthrough-creating-a-dataset-with-the-dataset-designer.md).  
   
 2.  Double-click the title bar of the data table on the designer.  
   

docs/data-tools/bind-objects-in-visual-studio.md

@@ -38,7 +38,7 @@ translation.priority.mt:
   - "tr-tr"
 ---
 # Bind objects in Visual Studio
-Visual Studio provides design-time tools for working with custom objects as the data source in your application. When you want to store data from a database in an object that you bind to UI controls, the recommended approach is to use Entity Framework to generate the class or classes. Entity Frameworkautogenerates all the boilerplate change-tracking code, which means that any changes to the local objects are automatically persisted to the database when you call AcceptChanges on the DbSet object.    For more information, see [Entity Framework Documentation](https://ef.readthedocs.org/en/latest/).  
+Visual Studio provides design-time tools for working with custom objects as the data source in your application. When you want to store data from a database in an object that you bind to UI controls, the recommended approach is to use Entity Framework to generate the class or classes. Entity Framework auto-generates all the boilerplate change-tracking code, which means that any changes to the local objects are automatically persisted to the database when you call AcceptChanges on the DbSet object.    For more information, see [Entity Framework Documentation](https://ef.readthedocs.org/en/latest/).  
 
 > [!TIP]
 >  The approaches to object binding in this article should only be considered if your application is already based on datasets.These approaches can also be used if you are already familiar with datasets, and the data you will be processing is tabular and not too complex or too big. For an even simpler example, involving loading data directly into objects by using a DataReader and manually updating the UI without databinding, see [Create a simple data application by using ADO.NET](../data-tools/create-a-simple-data-application-by-using-adonet.md).  
@@ -65,7 +65,7 @@ Visual Studio provides design-time tools for working with custom objects as the
 
 
 
-### Loaddata into objects  
+### Load data into objects  
  For this example, you load data into your objects by using TableAdapters. By default, TableAdapters are created with two kinds of methods that fetch data from a database and populate data tables.  
 
 -   The `TableAdapter.Fill` method fills an existing data table with the data returned.  
@@ -97,7 +97,7 @@ Visual Studio provides design-time tools for working with custom objects as the
  [!code-cs[VbRaddataConnecting#8](../data-tools/codesnippet/CSharp/bind-objects-in-visual-studio_2.cs)]
  [!code-vb[VbRaddataConnecting#8](../data-tools/codesnippet/VisualBasic/bind-objects-in-visual-studio_2.vb)]  
 
-### Addobjects to a collection  
+### Add objects to a collection  
  You add objects to a collection by calling the `Add` method of your custom collection class or of the <xref:System.Windows.Forms.BindingSource>.  
 
 
@@ -117,7 +117,7 @@ Visual Studio provides design-time tools for working with custom objects as the
  [!code-cs[VbRaddataConnecting#6](../data-tools/codesnippet/CSharp/bind-objects-in-visual-studio_4.cs)]
  [!code-vb[VbRaddataConnecting#6](../data-tools/codesnippet/VisualBasic/bind-objects-in-visual-studio_4.vb)]  
 
-### Removeobjects from a collection  
+### Remove objects from a collection  
  You remove objects from a collection by calling the `Remove` or `RemoveAt` method of your custom collection class or of <xref:System.Windows.Forms.BindingSource>.  
 
 > [!NOTE]
@@ -128,15 +128,15 @@ Visual Studio provides design-time tools for working with custom objects as the
  [!code-cs[VbRaddataConnecting#7](../data-tools/codesnippet/CSharp/bind-objects-in-visual-studio_5.cs)]
  [!code-vb[VbRaddataConnecting#7](../data-tools/codesnippet/VisualBasic/bind-objects-in-visual-studio_5.vb)]  
 
-### Displayobject data to users  
+### Display object data to users  
  To display the data in objects to users, create an object data source using the **Data Source Configuration** wizard, and then drag the entire object or individual properties onto your form from the **Data Sources** window.  
 
 ### Modify the data in objects  
  To edit data in custom objects that are data-bound to Windows Forms controls, simply edit the data in the bound control (or directly in the object's properties). Data-binding architecture updates the data in the object.  
 
  If your application requires the tracking of changes and the rolling back of proposed changes to their original values, then you must implement this functionality in your object model. For examples of how data tables keep track of proposed changes, see <xref:System.Data.DataRowState>, <xref:System.Data.DataSet.HasChanges%2A>, and <xref:System.Data.DataTable.GetChanges%2A>.  
 
-### Savedata in objects back to the database  
+### Save data in objects back to the database  
  Save data back to the database by passing the values from your object to the TableAdapter's DBDirect methods.  
 
  Visual Studio creates DBDirect methods that can be executed directly against the database. These methods do not require DataSet or DataTable objects.  

docs/data-tools/bind-wpf-controls-to-a-dataset.md

@@ -94,7 +94,7 @@ In this walkthrough, you will create a WPF application that contains data-bound
 
 2.  In the **Data Sources** window, click **Add New Data Source**.  
 
-     The **Data Source Configuration**wizard opens.  
+     The **Data Source Configuration** wizard opens.  
 
 3.  On the **Choose a Data Source Type** page, select **Database**, and then click **Next**.  
 
@@ -112,7 +112,7 @@ In this walkthrough, you will create a WPF application that contains data-bound
 
 8.  Click **Finish**.  
 
-     Visual Studio adds a new AdventureWorksLTDataSet.xsd file to the project, and it adds a corresponding **AdventureWorksLTDataSet** item to the **Data Sources** window. The AdventureWorksLTDataSet.xsd file defines a typed dataset named `AdventureWorksLTDataSet` and a TableAdapter named `ProductTableAdapter`. Later in this walkthrough, you will use the `ProductTableAdapter` to fill the dataset with data and save changes back to the database.  
+     Visual Studio adds a new `AdventureWorksLTDataSet.xsd` file to the project, and it adds a corresponding **AdventureWorksLTDataSet** item to the **Data Sources** window. The `AdventureWorksLTDataSet.xsd` file defines a typed dataset named `AdventureWorksLTDataSet` and a TableAdapter named `ProductTableAdapter`. Later in this walkthrough, you will use the `ProductTableAdapter` to fill the dataset with data and save changes back to the database.  
 
 9. Build the project.  
 
@@ -121,13 +121,13 @@ In this walkthrough, you will create a WPF application that contains data-bound
 
 #### To load product rows that have photos  
 
-1.  In **Solution Explorer**, double-click the AdventureWorksLTDataSet.xsd file.  
+1.  In **Solution Explorer**, double-click the `AdventureWorksLTDataSet.xsd` file.  
 
      The Dataset designer opens.  
 
-2.  In the designer, right-click the **Fill,GetData()** query and select **Configure**.  
+2.  In the designer, right-click the **Fill, GetData()** query and select **Configure**.  
 
-     The **TableAdapter Configuration**wizard opens.  
+     The **TableAdapter Configuration** wizard opens.  
 
 3.  In the **Enter a SQL Statement** page, add the following WHERE clause after the `SELECT` statement in the text box.  
 
@@ -160,7 +160,7 @@ In this walkthrough, you will create a WPF application that contains data-bound
   
 3.  Build the project.  
   
-## Createdata-bound controls  
+## Create data-bound controls  
  Create controls that display customer records by dragging the `Product` table from the **Data Sources** window to the WPF Designer.  
   
 #### To create data-bound controls  
@@ -220,7 +220,7 @@ In this walkthrough, you will create a WPF application that contains data-bound
      [!code-cs[Data_WPFDATASET#3](../data-tools/codesnippet/CSharp/bind-wpf-controls-to-a-dataset_3.cs)]
      [!code-vb[Data_WPFDATASET#3](../data-tools/codesnippet/VisualBasic/bind-wpf-controls-to-a-dataset_3.vb)]  
   
-## Savechanges to product records  
+## Save changes to product records  
  Add code that enables users to save changes to product records by using the **Save changes** button.  
   
 #### To add the ability to save changes to product records  

docs/data-tools/bind-wpf-controls-to-a-wcf-data-service.md

@@ -102,7 +102,7 @@ In this walkthrough, you will create a WPF application that contains data-bound
 
 3.  Change the name to `AdventureWorksModel.edmx`, and click **Add**.  
 
-     The **Entity Data Model**wizard opens.  
+     The **Entity Data Model** wizard opens.  
 
 4.  On the **Choose Model Contents** page, click **Generate from database**, and click **Next**.  
 
@@ -166,7 +166,7 @@ In this walkthrough, you will create a WPF application that contains data-bound
 
 6.  In the **Data Sources** window, click **Add New Data Source**.  
 
-     The **Data Source Configuration**wizard opens.  
+     The **Data Source Configuration** wizard opens.  
 
 7.  In the **Choose a Data Source Type** page of the wizard, select **Service**, and then click **Next**.  
 
@@ -189,7 +189,7 @@ In this walkthrough, you will create a WPF application that contains data-bound
 
 #### To create the window layout  
 
-1.  In **Solution Explorer**, double-click MainWindow.xaml.  
+1.  In **Solution Explorer**, double-click **MainWindow.xaml**.  
 
      The window opens in the WPF designer.  
 
@@ -258,7 +258,7 @@ In this walkthrough, you will create a WPF application that contains data-bound
      [!code-cs[Data_WPFWCF#2](../data-tools/codesnippet/CSharp/bind-wpf-controls-to-a-wcf-data-service_2.cs)]
      [!code-vb[Data_WPFWCF#2](../data-tools/codesnippet/VisualBasic/bind-wpf-controls-to-a-wcf-data-service_2.vb)]  
   
-## Navigatesales records  
+## Navigate sales records  
  Add code that enables users to scroll through sales records by using the **\<** and **>** buttons.  
   
 #### To enable users to navigate sales records  

docs/data-tools/could-not-retrieve-schema-information-for-database-object-object-name.md

@@ -27,7 +27,7 @@ translation.priority.mt:
   - "pt-br"
   - "tr-tr"
 ---
-# Could not retrieve schema information for database object <object name>
+# Could not retrieve schema information for database object \<object name>
 This message typically appears when an object in **Server Explorer/Database Explorer** is copied to the clipboard, deleted from the database, and then pasted onto the designer. Because the database object no longer exists, this message appears.  
 
 ### To correct this error  

docs/data-tools/create-a-simple-data-application-by-using-adonet.md

@@ -746,7 +746,7 @@ End Namespace
 |NC29|Close the NewCustomer form, and return focus to the Navigation form.|  
 
 ### FillOrCancel form  
- The FillorCancel form runs a query to return an order when you enter an order ID and select the **Find Order** button. The returned row appears in a read-only data grid. You can mark the order as canceled (X) if you select the **Cancel Order** button, or you can mark the order as filled (F) if you select the **Fill Order** button. If you select the **Find Order** button again, the updated row appears.  
+ The FillOrCancel form runs a query to return an order when you enter an order ID and select the **Find Order** button. The returned row appears in a read-only data grid. You can mark the order as canceled (X) if you select the **Cancel Order** button, or you can mark the order as filled (F) if you select the **Fill Order** button. If you select the **Find Order** button again, the updated row appears.  
 
 #### Create event handlers  
  Create empty Click event handlers for the four buttons on the form.