Merge pull request #23609 from rwestMSFT/rw-0808-includes-dotnet

v-regandowner · web-flow · commit c9a8cbd5c21e · 2022-08-08T15:40:02.000-04:00
[Bulk] INCLUDE file maintenance: clean up old .NET files and duplicates
diff --git a/docs/includes/dnprdnlong-md.md b/docs/includes/dnprdnlong-md.md
diff --git a/docs/includes/dnprdnshort_md.md b/docs/includes/dnprdnshort_md.md
diff --git a/docs/relational-databases/replication/configure-iis-7-for-web-synchronization.md b/docs/relational-databases/replication/configure-iis-7-for-web-synchronization.md
@@ -25,7 +25,7 @@ ms.author: "mathoma"
  For an overview of the entire configuration process, see [Configure Web Synchronization](../../relational-databases/replication/configure-web-synchronization.md).  
   
 > [!IMPORTANT]  
->  Make sure that your application uses only [!INCLUDE[dnprdnlong](../../includes/dnprdnlong-md.md)] or later versions, and that earlier versions of the [!INCLUDE[dnprdnshort](../../includes/dnprdnshort-md.md)] are not installed on the IIS server. Earlier versions of the [!INCLUDE[dnprdnshort](../../includes/dnprdnshort-md.md)] can cause errors, such as: "The format of a message during Web synchronization was invalid. Ensure that replication components are properly configured at the Web server."  
+>  Make sure that your application uses only [!INCLUDE[dnprdnshort](../../includes/dnprdnshort-md.md)] 2.0 or later versions, and that earlier versions of the [!INCLUDE[dnprdnshort](../../includes/dnprdnshort-md.md)] are not installed on the IIS server. Earlier versions of the [!INCLUDE[dnprdnshort](../../includes/dnprdnshort-md.md)] can cause errors, such as: "The format of a message during Web synchronization was invalid. Ensure that replication components are properly configured at the Web server."  
   
  To use Web synchronization, you must configure IIS by completing the following steps. Each step is described in detail in this topic.  
   
diff --git a/docs/relational-databases/xml/use-xml-data-in-applications.md b/docs/relational-databases/xml/use-xml-data-in-applications.md
@@ -146,13 +146,13 @@ Row 2
 
 To handle XML from an **xml** data type column by using ADO.NET and the [!INCLUDE[msCoName](../../includes/msconame-md.md)] [!INCLUDE[dnprdnshort](../../includes/dnprdnshort-md.md)] you can use the standard behavior of the **SqlCommand** class. For example, an **xml** data type column and its values can be retrieved in the same way any SQL column is retrieved by using a **SqlDataReader**.However, if you want to work with the contents of an **xml** data type column as XML, you'll first have to assign the contents to an **XmlReader** type.
 
-For more information and example code, see "XML Column Values in a Data Reader" in the [!INCLUDE[msCoName](../../includes/msconame-md.md)] [!INCLUDE[dnprdnlong](../../includes/dnprdnlong-md.md)] SDK documentation.
+For more information and example code, see "XML Column Values in a Data Reader" in the [!INCLUDE[msCoName](../../includes/msconame-md.md)] [!INCLUDE[dnprdnshort](../../includes/dnprdnshort-md.md)] 2.0 SDK documentation.
 
 ## Handle an xml type column in parameters by Using ADO.NET
 
 To handle an **xml** data type passed as a parameter in ADO.NET and the [!INCLUDE[dnprdnshort](../../includes/dnprdnshort-md.md)], you can supply the value as an instance of the **SqlXml** data type. No special handling is involved, because **xml** data type columns in [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] can accept parameter values in the same way as other columns and data types, such as **string** or **integer**.
 
-For more information and example code, see "XML Values as Command Parameters" in the [!INCLUDE[msCoName](../../includes/msconame-md.md)] [!INCLUDE[dnprdnlong](../../includes/dnprdnlong-md.md)] SDK documentation.
+For more information and example code, see "XML Values as Command Parameters" in the [!INCLUDE[msCoName](../../includes/msconame-md.md)] [!INCLUDE[dnprdnshort](../../includes/dnprdnshort-md.md)] 2.0 SDK documentation.
 
 ## See also
 
diff --git a/docs/ssma/db2/installing-ssma-for-db2-client-db2tosql.md b/docs/ssma/db2/installing-ssma-for-db2-client-db2tosql.md
@@ -33,7 +33,7 @@ Before you install SSMA, make sure that the computer meets the following require
 
 - Windows 7 or later versions, or Windows Server 2008 or later versions.
 - [!INCLUDE[msCoName](../../includes/msconame_md.md)] Windows Installer 3.1 or later versions.
-- The [!INCLUDE[msCoName](../../includes/msconame_md.md)] [!INCLUDE[dnprdnshort](../../includes/dnprdnshort_md.md)] version 4.7.2 or a later version. You can obtain it from the [.NET Framework Developer Center](https://go.microsoft.com/fwlink/?LinkId=48882).
+- The [!INCLUDE[msCoName](../../includes/msconame_md.md)] [!INCLUDE[dnprdnshort](../../includes/dnprdnshort-md.md)] version 4.7.2 or a later version. You can obtain it from the [.NET Framework Developer Center](https://go.microsoft.com/fwlink/?LinkId=48882).
 - Microsoft OLE DB Provider for DB2 version 5 or a later version, and connectivity to the DB2 databases that you want to migrate.
 - Access to and sufficient permissions on the computer that hosts the target instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] or Azure SQL Database where you will be migrating database objects and data. For more information, see [Connecting to SQL Server &#40;DB2ToSQL&#41;](../../ssma/db2/connecting-to-sql-server-db2tosql.md).
 - 4 GB RAM recommended.
diff --git a/docs/ssma/mysql/installing-ssma-components-on-sql-server-mysqltosql.md b/docs/ssma/mysql/installing-ssma-components-on-sql-server-mysqltosql.md
@@ -30,7 +30,7 @@ Also, when you migrate data to [!INCLUDE[ssNoVersion](../../includes/ssnoversion
 Before you install the SSMA for MySQL server components on [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], make sure that the computer meets the following requirements:
 
 - [!INCLUDE[msCoName](../../includes/msconame_md.md)] Windows Installer 3.1 or a later version.
-- The [!INCLUDE[msCoName](../../includes/msconame_md.md)] [!INCLUDE[dnprdnshort](../../includes/dnprdnshort_md.md)] version 4.7.2 or a later version. You can obtain it from the [.NET Framework Developer Center](https://go.microsoft.com/fwlink/?LinkId=48882).
+- The [!INCLUDE[msCoName](../../includes/msconame_md.md)] [!INCLUDE[dnprdnshort](../../includes/dnprdnshort-md.md)] version 4.7.2 or a later version. You can obtain it from the [.NET Framework Developer Center](https://go.microsoft.com/fwlink/?LinkId=48882).
 - The MySQL Client Provider, and connectivity to the MySQL database that you want to migrate. You can install providers from the MySQL product media or MySQL Web site.
 - The [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Browser service must be running during installation. This is used to populate a list of the instances of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] in the Setup wizard. You can disable the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Browser service after installation.  
 
diff --git a/docs/ssma/mysql/installing-ssma-for-mysql-client-mysqltosql.md b/docs/ssma/mysql/installing-ssma-for-mysql-client-mysqltosql.md
@@ -35,7 +35,7 @@ Before you install SSMA, make sure that the computer meets the following require
 
 - Windows 7 or later versions, or Windows Server 2008 or later versions.
 - [!INCLUDE[msCoName](../../includes/msconame_md.md)] Windows Installer 3.1 or a later version.
-- The [!INCLUDE[msCoName](../../includes/msconame_md.md)] [!INCLUDE[dnprdnshort](../../includes/dnprdnshort_md.md)] version 4.7.2 or a later version. You can obtain it from the [.NET Framework Developer Center](https://go.microsoft.com/fwlink/?LinkId=48882).
+- The [!INCLUDE[msCoName](../../includes/msconame_md.md)] [!INCLUDE[dnprdnshort](../../includes/dnprdnshort-md.md)] version 4.7.2 or a later version. You can obtain it from the [.NET Framework Developer Center](https://go.microsoft.com/fwlink/?LinkId=48882).
 - MySQL ODBC 5.1 Driver and connectivity to the MySQL databases that you want to migrate. You can install the MySQL from the MySQL Web site. For information about connectivity, see [Connecting to MySQL &#40;MySQLToSQL&#41;](../../ssma/mysql/connecting-to-mysql-mysqltosql.md).
 - Access to and sufficient permissions on the computer that hosts the target instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] where you will be migrating database objects and data. For more information, see [Connecting to SQL Server &#40;MySQLToSQL&#41;](../../ssma/mysql/connecting-to-sql-server-mysqltosql.md).
 - In case of [!INCLUDE[ssAzure](../../includes/ssazure_md.md)] projects, access to and sufficient permissions to the instance of [!INCLUDE[ssAzure](../../includes/ssazure_md.md)] where you will be migrating database objects and data. For more information, see [Connecting to Azure SQL Database &#40;MySQLToSQL&#41;](../../ssma/mysql/connecting-to-azure-sql-db-mysqltosql.md).
diff --git a/docs/ssma/oracle/installing-ssma-components-on-sql-server-oracletosql.md b/docs/ssma/oracle/installing-ssma-components-on-sql-server-oracletosql.md
@@ -32,7 +32,7 @@ Before you install the SSMA for Oracle server components on [!INCLUDE[ssNoVersio
 
 - [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] instance is installed.
 - [!INCLUDE[msCoName](../../includes/msconame_md.md)] Windows Installer 3.1 or a later version.
-- The [!INCLUDE[msCoName](../../includes/msconame_md.md)] [!INCLUDE[dnprdnshort](../../includes/dnprdnshort_md.md)] version 4.7.2 or a later version. You can obtain it from the [.NET Framework Developer Center](https://go.microsoft.com/fwlink/?LinkId=48882).
+- The [!INCLUDE[msCoName](../../includes/msconame_md.md)] [!INCLUDE[dnprdnshort](../../includes/dnprdnshort-md.md)] version 4.7.2 or a later version. You can obtain it from the [.NET Framework Developer Center](https://go.microsoft.com/fwlink/?LinkId=48882).
 - The OLE DB provider for Oracle (if using OLE DB), and connectivity to the Oracle database that you want to migrate. You can install providers from the Oracle product media or Oracle Web site.
 - The [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Browser service must be running during installation. This is used to populate a list of the instances of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] in the Setup wizard. You can disable the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Browser service after installation.
 
diff --git a/docs/ssma/oracle/installing-ssma-for-oracle-client-oracletosql.md b/docs/ssma/oracle/installing-ssma-for-oracle-client-oracletosql.md
@@ -33,7 +33,7 @@ Before you install SSMA, make sure that the computer meets the following require
 
 - Windows 7 or later versions, or Windows Server 2008 or later versions.
 - [!INCLUDE[msCoName](../../includes/msconame_md.md)] Windows Installer 3.1 or a later version.
-- The [!INCLUDE[msCoName](../../includes/msconame_md.md)] [!INCLUDE[dnprdnshort](../../includes/dnprdnshort_md.md)] version 4.7.2 or a later version. You can obtain it from the [.NET Framework Developer Center](https://go.microsoft.com/fwlink/?LinkId=48882).
+- The [!INCLUDE[msCoName](../../includes/msconame_md.md)] [!INCLUDE[dnprdnshort](../../includes/dnprdnshort-md.md)] version 4.7.2 or a later version. You can obtain it from the [.NET Framework Developer Center](https://go.microsoft.com/fwlink/?LinkId=48882).
 - Connectivity to the Oracle databases that you want to migrate.
 - Access to and sufficient permissions on the computer that hosts the target instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] or [!INCLUDE[ssAzure](../../includes/ssazure_md.md)] where you will be migrating database objects and data. For more information, see [Connecting to SQL Server &#40;OracleToSQL&#41;](../../ssma/oracle/connecting-to-sql-server-oracletosql.md).
 - 4 GB RAM recommended.  
diff --git a/docs/ssma/sybase/installing-ssma-components-on-sql-server-sybasetosql.md b/docs/ssma/sybase/installing-ssma-components-on-sql-server-sybasetosql.md
@@ -29,7 +29,7 @@ Before you install the SSMA for Sybase server components on [!INCLUDE[ssNoVersio
 
 - [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] instance is installed.
 - [!INCLUDE[msCoName](../../includes/msconame_md.md)] Windows Installer 3.1 or a later version.
-- The [!INCLUDE[msCoName](../../includes/msconame_md.md)] [!INCLUDE[dnprdnshort](../../includes/dnprdnshort_md.md)] version 4.7.2 or a later version. You can obtain it from the [.NET Framework Developer Center](https://go.microsoft.com/fwlink/?LinkId=48882).
+- The [!INCLUDE[msCoName](../../includes/msconame_md.md)] [!INCLUDE[dnprdnshort](../../includes/dnprdnshort-md.md)] version 4.7.2 or a later version. You can obtain it from the [.NET Framework Developer Center](https://go.microsoft.com/fwlink/?LinkId=48882).
 - The Sybase OLE DB/ADO.Net/ODBC provider and connectivity to the SAP ASE database server that contains the databases you want to migrate. You can install providers from the SAP ASE product media. For information about connectivity, see [Connecting to Sybase ASE &#40;SybaseToSQL&#41;](../../ssma/sybase/connecting-to-sybase-ase-sybasetosql.md).
 - The [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Browser service must be running during installation. This is used to populate a list of the instances of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] in the Setup wizard. You can disable the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Browser service after installation.
 
diff --git a/docs/ssms/add-an-external-tool-to-the-tools-menu-sql-server-management-studio.md b/docs/ssms/add-an-external-tool-to-the-tools-menu-sql-server-management-studio.md
@@ -21,7 +21,7 @@ ms.date: "01/19/2017"
 
 [!INCLUDE[SQL Server Azure SQL Database Synapse Analytics PDW](../includes/applies-to-version/sql-asdb-asdbmi-asa-pdw.md)]
 
-You can launch any Microsoft Windows or Microsoft [!INCLUDE[dnprdnshort](../includes/dnprdnshort_md.md)] application from SQL Server Management Studio. External applications can be added to, and run from, the **Tools** menu.  
+You can launch any Microsoft Windows or Microsoft [!INCLUDE[dnprdnshort](../includes/dnprdnshort-md.md)] application from SQL Server Management Studio. External applications can be added to, and run from, the **Tools** menu.  
   
 ## To add an external tool to the Tools menu  
 
diff --git a/docs/ssms/object/custom-reports-in-management-studio.md b/docs/ssms/object/custom-reports-in-management-studio.md
@@ -63,7 +63,7 @@ Custom reports run by using the permissions of the current user. To prevent a ma
   
 Both the user and the account that is used by the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] service require read access to the file system folder that contains the report files.  
   
-Any valid [!INCLUDE[dnprdnshort](../../includes/dnprdnshort_md.md)] command can be embedded in a report, but the command will not be executed.  
+Any valid [!INCLUDE[dnprdnshort](../../includes/dnprdnshort-md.md)] command can be embedded in a report, but the command will not be executed.  
   
 > [!CAUTION]  
 > Any valid [!INCLUDE[tsql](../../includes/tsql-md.md)] statement can be embedded in and executed from a report. Running a report under a high-privileged user account makes it possible for any of these embedded instructions to execute without challenge.  
