Remove codeplex links (dotnet#7371)

Author: gewarren

xml/System.Data.Objects.DataClasses/EntityCollection`1.xml

@@ -63,10 +63,8 @@
 
  This class cannot be inherited.
 
-
-
 ## Examples
- This example is based on the [Adventure Works Sales Model](https://archive.codeplex.com/?p=msftdbprodsamples). To run the code in this example, you must have already added the AdventureWorks Sales Model to your project and configured your project to use the Entity Framework. To do this, complete the procedures in [How to: Manually Configure an Entity Framework Project](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/bb738546(v=vs.100)) and [How to: Manually Define the Model and Mapping Files](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/bb399785(v=vs.100)).
+ This example is based on the Adventure Works Sales Model. To run the code in this example, you must have already added the AdventureWorks Sales Model to your project and configured your project to use the Entity Framework. To do this, complete the procedures in [How to: Manually Configure an Entity Framework Project](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/bb738546(v=vs.100)) and [How to: Manually Define the Model and Mapping Files](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/bb399785(v=vs.100)).
 
  This example does the following:
 
@@ -157,10 +155,8 @@
 
  The <xref:System.Data.Objects.DataClasses.EntityCollection%601.Add%2A> method can be called multiple times on the same object instance.
 
-
-
 ## Examples
- This example is based on the [Adventure Works Sales Model](https://archive.codeplex.com/?p=msftdbprodsamples). To run the code in this example, you must have already added the AdventureWorks Sales Model to your project and configured your project to use the Entity Framework. To do this, complete the procedures in [How to: Manually Configure an Entity Framework Project](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/bb738546(v=vs.100)) and [How to: Manually Define the Model and Mapping Files](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/bb399785(v=vs.100)).
+ This example is based on the Adventure Works Sales Model. To run the code in this example, you must have already added the AdventureWorks Sales Model to your project and configured your project to use the Entity Framework. To do this, complete the procedures in [How to: Manually Configure an Entity Framework Project](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/bb738546(v=vs.100)) and [How to: Manually Define the Model and Mapping Files](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/bb399785(v=vs.100)).
 
  This example creates two new `SalesOrderHeader` entities, adds them to the `Contact` entity, and, after removing an object, uses the <xref:System.Data.Objects.DataClasses.EntityCollection%601.Add%2A> method to add the object back to the collection.
 
@@ -223,7 +219,7 @@
 
  -or-
 
- The relationship cannot be defined based on the [Adventure Works Sales Model](https://archive.codeplex.com/?p=msftdbprodsamples) EDM metadata. This can occur when the association in the conceptual schema does not support a relationship between the two types.</exception>
+ The relationship cannot be defined based on the EDM metadata. This can occur when the association in the conceptual schema does not support a relationship between the two types.</exception>
       </Docs>
     </Member>
     <Member MemberName="Attach">
@@ -265,7 +261,7 @@
 
 
 ## Examples
- This example is based on the [Adventure Works Sales Model](https://archive.codeplex.com/?p=msftdbprodsamples). To run the code in this example, you must have already added the AdventureWorks Sales Model to your project and configured your project to use the Entity Framework. To do this, complete the procedures in [How to: Manually Configure an Entity Framework Project](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/bb738546(v=vs.100)) and [How to: Manually Define the Model and Mapping Files](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/bb399785(v=vs.100)).
+ This example is based on the Adventure Works Sales Model. To run the code in this example, you must have already added the AdventureWorks Sales Model to your project and configured your project to use the Entity Framework. To do this, complete the procedures in [How to: Manually Configure an Entity Framework Project](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/bb738546(v=vs.100)) and [How to: Manually Define the Model and Mapping Files](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/bb399785(v=vs.100)).
 
  This example attaches a collection of detached `SalesOrderDetail` objects and a detached `SalesOrderHeader` object to an object context, and then defines the relationships between the `SalesOrderHeader` object and each `SalesOrderDetail` object.
 
@@ -358,7 +354,7 @@
 
 
 ## Examples
- This example is based on the [Adventure Works Sales Model](https://archive.codeplex.com/?p=msftdbprodsamples). To run the code in this example, you must have already added the AdventureWorks Sales Model to your project and configured your project to use the Entity Framework. To do this, complete the procedures in [How to: Manually Configure an Entity Framework Project](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/bb738546(v=vs.100)) and [How to: Manually Define the Model and Mapping Files](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/bb399785(v=vs.100)).
+ This example is based on the Adventure Works Sales Model. To run the code in this example, you must have already added the AdventureWorks Sales Model to your project and configured your project to use the Entity Framework. To do this, complete the procedures in [How to: Manually Configure an Entity Framework Project](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/bb738546(v=vs.100)) and [How to: Manually Define the Model and Mapping Files](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/bb399785(v=vs.100)).
 
  This example does the following:
 
@@ -593,7 +589,7 @@ This method calls the internal `RelatedEnd.ValidateLoad` method before loading t
 
 
 ## Examples
- This example is based on the [Adventure Works Sales Model](https://archive.codeplex.com/?p=msftdbprodsamples). To run the code in this example, you must have already added the AdventureWorks Sales Model to your project and configured your project to use the Entity Framework. To do this, complete the procedures in [How to: Manually Configure an Entity Framework Project](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/bb738546(v=vs.100)) and [How to: Manually Define the Model and Mapping Files](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/bb399785(v=vs.100)).
+ This example is based on the Adventure Works Sales Model. To run the code in this example, you must have already added the AdventureWorks Sales Model to your project and configured your project to use the Entity Framework. To do this, complete the procedures in [How to: Manually Configure an Entity Framework Project](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/bb738546(v=vs.100)) and [How to: Manually Define the Model and Mapping Files](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/bb399785(v=vs.100)).
 
  This example loads the related `SalesOrderHeader` objects for the `Contact` entity.
 
@@ -718,7 +714,7 @@ This method calls the internal `RelatedEnd.ValidateLoad` method before loading t
 
 
 ## Examples
- This example is based on the [Adventure Works Sales Model](https://archive.codeplex.com/?p=msftdbprodsamples). To run the code in this example, you must have already added the AdventureWorks Sales Model to your project and configured your project to use the Entity Framework. To do this, complete the procedures in [How to: Manually Configure an Entity Framework Project](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/bb738546(v=vs.100)) and [How to: Manually Define the Model and Mapping Files](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/bb399785(v=vs.100)).
+ This example is based on the Adventure Works Sales Model. To run the code in this example, you must have already added the AdventureWorks Sales Model to your project and configured your project to use the Entity Framework. To do this, complete the procedures in [How to: Manually Configure an Entity Framework Project](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/bb738546(v=vs.100)) and [How to: Manually Define the Model and Mapping Files](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/bb399785(v=vs.100)).
 
  This example uses the <xref:System.Data.Objects.DataClasses.EntityCollection%601.Remove%2A> method to remove one of the entities from the collection and then calls the <xref:System.Data.Objects.DataClasses.EntityCollection%601.Contains%2A> method to determine whether the object was removed from the collection.
 

xml/System.Data.Objects.DataClasses/IRelatedEnd.xml

@@ -19,12 +19,9 @@
 ## Remarks
  <xref:System.Data.Objects.DataClasses.IRelatedEnd> defines the requirements for an object that represents an end in an association. This interface is implemented by the <xref:System.Data.Objects.DataClasses.RelatedEnd> class. <xref:System.Data.Objects.DataClasses.RelatedEnd> is the base class for the <xref:System.Data.Objects.DataClasses.EntityCollection%601> and <xref:System.Data.Objects.DataClasses.EntityReference%601> classes.
 
-
-
 ## Examples
- The example in this topic is based on the [Microsoft SQL Server Product Samples: Database](https://archive.codeplex.com/?p=msftdbprodsamples), which was generated by the [Entity Data Model Wizard](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/bb399247(v=vs.100)).
 
- The following example adds new `SalesOrderHeader` entities to the `Contact` entity. Then it gets all related ends from the `Contact` entity and displays relationship name, source role name, and target role name for each related end.
+The following example adds new `SalesOrderHeader` entities to the `Contact` entity. Then it gets all related ends from the `Contact` entity and displays relationship name, source role name, and target role name for each related end.
 
  :::code language="csharp" source="~/snippets/csharp/System.Data/EntityKey/Overview/Source.cs" id="Snippetirelatedend":::
  :::code language="vb" source="~/snippets/visualbasic/VS_Snippets_Data/DP ObjectServices Concepts/VB/Source.vb" id="Snippetirelatedend":::
@@ -394,9 +391,8 @@
           <format type="text/markdown"><![CDATA[
 
 ## Examples
- The example in this topic is based on the [Microsoft SQL Server Product Samples: Database](https://archive.codeplex.com/?p=msftdbprodsamples), which was generated by the [Entity Data Model Wizard](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/bb399247(v=vs.100)).
 
- The following example adds new `SalesOrderHeader` entities to the `Contact` entity. Then it gets all related ends from the `Contact` entity and displays the relationship name, source role name, and target role name for each related end.
+The following example adds new `SalesOrderHeader` entities to the `Contact` entity. Then it gets all related ends from the `Contact` entity and displays the relationship name, source role name, and target role name for each related end.
 
  :::code language="csharp" source="~/snippets/csharp/System.Data/EntityKey/Overview/Source.cs" id="Snippetirelatedend":::
  :::code language="vb" source="~/snippets/visualbasic/VS_Snippets_Data/DP ObjectServices Concepts/VB/Source.vb" id="Snippetirelatedend":::

xml/System.Data.Objects.DataClasses/RelatedEnd.xml

@@ -493,10 +493,7 @@ The `Merge<TEntity>` method is called by Object Services during relationship ope
 ## Remarks
  The role name is specified by the `Role` attribute of the `End` element in the association that defines this relationship in the conceptual model. For more information, see [Association Element (CSDL)](https://msdn.microsoft.com/library/c305169a-8af7-432f-9ba7-800a163aed41).
 
-
-
 ## Examples
- The example in this topic is based on the [Microsoft SQL Server Product Samples: Database](https://archive.codeplex.com/?p=msftdbprodsamples), which was generated by the [Entity Data Model Wizard](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/bb399247(v=vs.100)).
 
  The following example adds new `SalesOrderHeader` entities to the `Contact` entity. Then it gets all related ends from the `Contact` entity and displays relationship name, source role name, and target role name for each related end.
 
@@ -829,7 +826,7 @@ The `Merge<TEntity>` method is called by Object Services during relationship ope
 
 
 ## Examples
- The example in this topic is based on the [Microsoft SQL Server Product Samples: Database](https://archive.codeplex.com/?p=msftdbprodsamples). The example adds new `SalesOrderHeader` entities to the `Contact` entity. Then it gets all related ends from the `Contact` entity and displays relationship name, source role name, and target role name for each related end.
+ This example adds new `SalesOrderHeader` entities to the `Contact` entity. Then it gets all related ends from the `Contact` entity and displays relationship name, source role name, and target role name for each related end.
 
  :::code language="csharp" source="~/snippets/csharp/System.Data/EntityKey/Overview/Source.cs" id="Snippetirelatedend":::
  :::code language="vb" source="~/snippets/visualbasic/VS_Snippets_Data/DP ObjectServices Concepts/VB/Source.vb" id="Snippetirelatedend":::

xml/System.Data.Objects.DataClasses/RelationshipManager.xml

@@ -31,7 +31,7 @@
 
 
 ## Examples
- The example in this topic is based on the [Microsoft SQL Server Product Samples: Database](https://archive.codeplex.com/?p=msftdbprodsamples). The example adds new `SalesOrderHeader` entities to the `Contact` entity. Then it gets all related ends from the `Contact` entity and displays the relationship name, source role name, and target role name for each related end.
+ This example adds new `SalesOrderHeader` entities to the `Contact` entity. Then it gets all related ends from the `Contact` entity and displays the relationship name, source role name, and target role name for each related end.
 
  :::code language="csharp" source="~/snippets/csharp/System.Data/EntityKey/Overview/Source.cs" id="Snippetirelatedend":::
  :::code language="vb" source="~/snippets/visualbasic/VS_Snippets_Data/DP ObjectServices Concepts/VB/Source.vb" id="Snippetirelatedend":::
@@ -113,7 +113,7 @@
 
 
 ## Examples
- The example in this topic is based on the [Microsoft SQL Server Product Samples: Database](https://archive.codeplex.com/?p=msftdbprodsamples). The example adds new `SalesOrderHeader` entities to the `Contact` entity. Then it gets all related ends from the `Contact` entity and displays relationship name, source role name, and target role name for each related end,
+ This example adds new `SalesOrderHeader` entities to the `Contact` entity. Then it gets all related ends from the `Contact` entity and displays relationship name, source role name, and target role name for each related end,
 
  :::code language="csharp" source="~/snippets/csharp/System.Data/EntityKey/Overview/Source.cs" id="Snippetirelatedend":::
  :::code language="vb" source="~/snippets/visualbasic/VS_Snippets_Data/DP ObjectServices Concepts/VB/Source.vb" id="Snippetirelatedend":::