migration miss table

dotnet · rpetrusha · Jul 23, 2018 · Jul 20, 2018 · Jul 20, 2018 · Jul 20, 2018
commit 6ee6e87a5aa7c886b085b1fd457e1d4d75c78c2a
diff --git a/includes/fxrefbanner.md b/includes/fxrefbanner.md
@@ -0,0 +1,3 @@
+> [!NOTE]
+>  The .NET API Reference documentation has a new home. Visit the [.NET API Browser](https://docs.microsoft.com/dotnet/api/?view=netframework-4.7.1) on docs.microsoft.com to see the new experience.
+
diff --git a/includes/ssnoversion-md.md b/includes/ssnoversion-md.md
@@ -0,0 +1 @@
+SQL Server
diff --git a/xml/System.Data.SqlClient/SqlConnection.xml b/xml/System.Data.SqlClient/SqlConnection.xml
diff --git a/xml/System.Windows.Forms/Binding.xml b/xml/System.Windows.Forms/Binding.xml
@@ -1,4 +1,4 @@
-<Type Name="Binding" FullName="System.Windows.Forms.Binding">
+<Type Name="Binding" FullName="System.Windows.Forms.Binding">
   <TypeSignature Language="C#" Value="public class Binding" />
   <TypeSignature Language="ILAsm" Value=".class public auto ansi beforefieldinit Binding extends System.Object" />
   <TypeSignature Language="DocId" Value="T:System.Windows.Forms.Binding" />
@@ -44,7 +44,13 @@
 
  Second, you can specify an instance of any one of the classes in the following table as the data source.  
 
-  Third, you must specify the navigation path, which can be an empty string (""), a single property name, or a period-delimited hierarchy of names. If you set the navigation path to an empty string, the <xref:System.Object.ToString%2A> method will be called on the underlying data source object.  
+|Description|C# example|  
+|-----------------|-----------------|  
+|Any class that implements <xref:System.ComponentModel.IBindingList> or <xref:System.ComponentModel.ITypedList>. These include the following: <xref:System.Data.DataSet>, <xref:System.Data.DataTable>, <xref:System.Data.DataView>, or <xref:System.Data.DataViewManager>.|`DataSet ds = new DataSet("myDataSet");`|  
+|Any class that implements <xref:System.Collections.IList> to create an indexed collection of objects. The collection must be created and filled before creating the <xref:System.Windows.Forms.Binding>. The objects in the list must all be of the same type; otherwise, an exception will be thrown.|`ArrayList ar1 = new ArrayList;  Customer1 cust1 = new Customer("Louis");  ar1.Add(cust1);`|  
+|A strongly typed <xref:System.Collections.IList> of strongly typed objects|`Customer [] custList = new Customer[3];`|  
+
+ Third, you must specify the navigation path, which can be an empty string (""), a single property name, or a period-delimited hierarchy of names. If you set the navigation path to an empty string, the <xref:System.Object.ToString%2A> method will be called on the underlying data source object.  
 
  If the data source is a <xref:System.Data.DataTable>, which can contain multiple <xref:System.Data.DataColumn> objects, the navigation path must be used to resolve to a specific column.  
 
@@ -144,7 +150,7 @@
  [!code-cpp[Classic Binding Example#1](~/samples/snippets/cpp/VS_Snippets_Winforms/Classic Binding Example/CPP/source.cpp#1)]
  [!code-csharp[Classic Binding Example#1](~/samples/snippets/csharp/VS_Snippets_Winforms/Classic Binding Example/CS/source.cs#1)]
  [!code-vb[Classic Binding Example#1](~/samples/snippets/visualbasic/VS_Snippets_Winforms/Classic Binding Example/VB/source.vb#1)]  
-  
+
  ]]></format>
     </remarks>
     <altmember cref="T:System.Windows.Forms.BindingContext" />

diff --git a/xml/System.Xml.Xsl/XslTransform.xml b/xml/System.Xml.Xsl/XslTransform.xml
@@ -1,4 +1,4 @@
-<Type Name="XslTransform" FullName="System.Xml.Xsl.XslTransform">
+<Type Name="XslTransform" FullName="System.Xml.Xsl.XslTransform">
   <TypeSignature Language="C#" Value="public sealed class XslTransform" />
   <TypeSignature Language="ILAsm" Value=".class public auto ansi sealed beforefieldinit XslTransform extends System.Object" />
   <TypeSignature Language="DocId" Value="T:System.Xml.Xsl.XslTransform" />
@@ -787,8 +787,14 @@
 
  There are different ways to provide evidence. The following table describes what type of evidence to provide for common user scenarios.  
 
-
+|Scenario|Type of evidence to provide|  
+|--------------|---------------------------------|  
+|The XSLT style sheet is self-contained or comes from a code base that you trust.|Use the evidence from your assembly.<br /><br /> `XsltTransform xslt = new XslTransform(); xslt.Load(xslReader, resolver, this.GetType().Assembly.Evidence);`|  
+|The XSLT style sheet comes from an outside source. The origin of the source is known, and there is a verifiable URL.|Create evidence using the URL.<br /><br /> `XsltTransform xslt = new XslTransform(); Evidence evidence = XmlSecureResolver.CreateEvidenceForUrl(stylesheetURL); xslt.Load(xslReader,resolver,evidence);`|  
+|The XSLT style sheet comes from an outside source. The origin of the source is not known.|Set evidence to `null`. Script blocks are not processed, the XSLT `document()` function is not supported, and privileged extension objects are disallowed.<br /><br /> Additionally, you can also set the `resolver` parameter to `null`. This ensures that `xsl:import` and `xsl:include` elements are not processed.|  
+|The XSLT style sheet comes from an outside source. The origin of the source is not known, but you require script support.|Request evidence from the caller. The API of the caller must provide a way to provide evidence, typically the <xref:System.Security.Policy.Evidence> class.|  
 
+
 ## Examples  
  The following example performs an XSLT transformation where `xsltReader` is an <xref:System.Xml.XmlReader> containing a style sheet and `secureURL` is a trusted URL that can be used to create <xref:System.Security.Policy.Evidence>. The <xref:System.Xml.XmlSecureResolver.CreateEvidenceForUrl%2A?displayProperty=nameWithType> method is used to create <xref:System.Security.Policy.Evidence> which is applied to the style sheet.  
 
@@ -858,7 +864,14 @@
 
  There are different ways to provide evidence. The following table describes what type of evidence to provide for common user scenarios.  
 
-  ]]></format>
+|Scenario|Type of evidence to provide|  
+|--------------|---------------------------------|  
+|The XSLT style sheet is self-contained or comes from a code base that you trust.|Use the evidence from your assembly.<br /><br /> `XsltTransform xslt = new XslTransform(); xslt.Load(style sheet, resolver, this.GetType().Assembly.Evidence);`|  
+|The XSLT style sheet comes from an outside source. The origin of the source is known, and there is a verifiable URL.|Create evidence using the URL.<br /><br /> `XsltTransform xslt = new XslTransform(); Evidence evidence = XmlSecureResolver.CreateEvidenceForUrl(style sheetURL); xslt.Load(style sheet,resolver,evidence);`|  
+|The XSLT style sheet comes from an outside source. The origin of the source is not known.|Set evidence to `null`. Script blocks are not processed, the XSLT `document()` function is not supported, and privileged extension objects are disallowed.<br /><br /> Additionally, you can also set the `resolver` parameter to `null`. This ensures that `xsl:import` and `xsl:include` elements are not processed.|  
+|The XSLT style sheet comes from an outside source. The origin of the source is not known, but you require script support.|Request evidence from the caller. The API of the caller must provide a way to provide evidence, typically the <xref:System.Security.Policy.Evidence> class.|  
+
+ ]]></format>
         </remarks>
         <exception cref="T:System.Xml.Xsl.XsltCompileException">The loaded resource is not a valid style sheet.</exception>
         <exception cref="T:System.Security.SecurityException">The referenced style sheet requires functionality that is not allowed by the evidence provided.  
@@ -922,11 +935,18 @@
 
  There are different ways to provide evidence. The following table describes what type of evidence to provide for common user scenarios.  
 
-
+|Scenario|Type of evidence to provide|  
+|--------------|---------------------------------|  
+|The XSLT style sheet is self-contained or comes from a code base that you trust.|Use the evidence from your assembly.<br /><br /> `XsltTransform xslt = new XslTransform(); xslt.Load(xslNav, resolver, this.GetType().Assembly.Evidence);`|  
+|The XSLT style sheet comes from an outside source. The origin of the source is known, and there is a verifiable URL.|Create evidence using the URL.<br /><br /> `XsltTransform xslt = new XslTransform(); Evidence evidence = XmlSecureResolver.CreateEvidenceForUrl(style sheetURL); xslt.Load(xslNav,resolver,evidence);`|  
+|The XSLT style sheet comes from an outside source. The origin of the source is not known.|Set evidence to `null`. Script blocks are not processed, the XSLT `document()` function is not supported, and privileged extension objects are disallowed.<br /><br /> Additionally, you can also set the `resolver` parameter to `null`. This ensures that `xsl:import` and `xsl:include` elements are not processed.|  
+|The XSLT style sheet comes from an outside source. The origin of the source is not known, but you require script support.|Request evidence from the caller. The API of the caller must provide a way to provide evidence, typically the `Evidence` class.|  
+
+
 
 ## Examples  
  The following example performs an XSLT transformation using a style sheet from an outside source. Because the style sheet comes from an untrusted source, the `resolver` and `evidence` parameters are set to `null`.  
-  
+
  [!code-csharp[XslTransform.Load5#1](~/samples/snippets/csharp/VS_Snippets_Data/XslTransform.Load5/CS/trans_noev.cs#1)]
  [!code-vb[XslTransform.Load5#1](~/samples/snippets/visualbasic/VS_Snippets_Data/XslTransform.Load5/VB/trans_noev.vb#1)]  
 

diff --git a/xml/System/ArgumentNullException.xml b/xml/System/ArgumentNullException.xml
@@ -1,4 +1,4 @@
-<Type Name="ArgumentNullException" FullName="System.ArgumentNullException">
+<Type Name="ArgumentNullException" FullName="System.ArgumentNullException">
   <TypeSignature Language="C#" Value="public class ArgumentNullException : ArgumentException" />
   <TypeSignature Language="ILAsm" Value=".class public auto ansi serializable beforefieldinit ArgumentNullException extends System.ArgumentException" />
   <TypeSignature Language="DocId" Value="T:System.ArgumentNullException" />
@@ -163,7 +163,13 @@
 
  The following table shows the initial property values for an instance of <xref:System.ArgumentNullException>.  
 
-  ]]></format>
+|Property|Value|  
+|--------------|-----------|  
+|<xref:System.Exception.InnerException%2A>|A null reference (`Nothing` in Visual Basic).|  
+|<xref:System.ArgumentException.Message%2A>|A localized error message string that identifies the null argument. For example, if the `paramName` argument is "arg1", the English language message string is:<br /><br /> `Value cannot be null.Parameter name: arg01`|  
+|<xref:System.ArgumentException.ParamName%2A>|The parameter name string.|  
+
+ ]]></format>
         </remarks>
       </Docs>
     </Member>
Original file line number	Diff line number	Diff line change
		@@ -0,0 +1,3 @@
		> [!NOTE]
		> The .NET API Reference documentation has a new home. Visit the [.NET API Browser](https://docs.microsoft.com/dotnet/api/?view=netframework-4.7.1) on docs.microsoft.com to see the new experience.