dotnet · tdykstra · May 13, 2021 · May 13, 2021 · May 13, 2021
@@ -214,6 +214,7 @@
         "docs/framework/wcf/diagnostics/performance-counters/**.md": "reference",
         "docs/framework/wcf/diagnostics/tracing/**.md": "reference",
         "docs/framework/wcf/diagnostics/wmi/**.md": "reference",
+        "docs/framework/wcf/whats-new/**.md": "reference",
         "docs/framework/**/how-to*.md": "how-to",
         "docs/fsharp/language-reference/**/**.md": "language-reference",
         "docs/fundamentals/code-analysis/**.md": "reference",

@@ -2,7 +2,7 @@
 description: "Learn more about: Specifying a Custom Crypto Algorithm"
 title: "Specifying a Custom Crypto Algorithm"
 ms.date: "03/30/2017"
-ms.assetid: d662a305-8e09-451d-9a59-b0f12b012f1d
+ms.topic: how-to
 ---
 # Specifying a Custom Crypto Algorithm
 
@@ -85,7 +85,7 @@ public class MyCustomAlgorithmSuite : SecurityAlgorithmSuite
 
 ## Register the Custom Algorithm  
 
- Registration can be done in a configuration file or in imperative code. Registering a custom algorithm is done by creating a mapping between a class that implements a crypto service provider and an alias. The alias is then mapped to a URI which is used when specifying the algorithm in the WCF service’s binding. The following configuration snippet illustrates how to register a custom algorithm in config:  
+ Registration can be done in a configuration file or in imperative code. Registering a custom algorithm is done by creating a mapping between a class that implements a crypto service provider and an alias. The alias is then mapped to a URI which is used when specifying the algorithm in the WCF service's binding. The following configuration snippet illustrates how to register a custom algorithm in config:  
 
 ```xml  
 <configuration>  

@@ -5,7 +5,7 @@ ms.date: "03/30/2017"
 dev_langs:
   - "csharp"
   - "vb"
-ms.assetid: 2b5ba5c3-0c6c-48e9-9e46-54acaec443ba
+ms.topic: how-to
 ---
 # Walkthrough: Creating Custom Client and Service Credentials
 

@@ -2,7 +2,7 @@
 description: "Learn more about: WS-MetadataExchange Bindings"
 title: "WS-MetadataExchange Bindings"
 ms.date: "03/30/2017"
-ms.assetid: 10f8de5d-b81d-4ea7-b37e-7f2c00c39714
+ms.topic: reference
 ---
 # WS-MetadataExchange Bindings
 

@@ -2,7 +2,7 @@
 title: "Client Configuration"
 description: Learn how to use WCF client configuration to specify the address, binding, behavior, and contract for an endpoint, which is used to connect to a service.
 ms.date: "03/30/2017"
-ms.assetid: 5da5bd3b-65d9-43b7-91b9-cc9e989b1350
+ms.topic: how-to
 ---
 # Client Configuration
 

@@ -6,7 +6,6 @@ ms.topic: how-to
 dev_langs: 
   - "csharp"
   - "vb"
-ms.assetid: 48e1cd90-de80-4d6c-846e-631878955762
 ---
 # How to: Configure WCF Service to Interoperate with ASP.NET Web Service Clients
 

@@ -2,15 +2,15 @@
 description: "Learn more about: Configuring Discovery in a Configuration File"
 title: "Configuring Discovery in a Configuration File"
 ms.date: "03/30/2017"
-ms.assetid: b9884c11-8011-4763-bc2c-c526b80175d0
+ms.topic: how-to
 ---
 # Configuring Discovery in a Configuration File
 
 There are four major groups of configuration settings used in discovery. This topic will briefly describe each and show examples of how to configure them. Following each section will be a link to more in-depth documentation about each area.  
 
 ## Behavior Configuration  
 
- Discovery uses service behaviors and endpoint behaviors. The <xref:System.ServiceModel.Discovery.ServiceDiscoveryBehavior> behavior enables discovery for all of a service’s endpoints and allows you to specify announcement endpoints.  The following example shows how to add the <xref:System.ServiceModel.Discovery.ServiceDiscoveryBehavior> and specify an announcement endpoint.  
+ Discovery uses service behaviors and endpoint behaviors. The <xref:System.ServiceModel.Discovery.ServiceDiscoveryBehavior> behavior enables discovery for all of a service's endpoints and allows you to specify announcement endpoints.  The following example shows how to add the <xref:System.ServiceModel.Discovery.ServiceDiscoveryBehavior> and specify an announcement endpoint.  
 
 ```xml  
 <behaviors>  
@@ -232,7 +232,7 @@ There are four major groups of configuration settings used in discovery. This to
 </standardEndpoints>
 ```  
 
- Once you’ve added the standard endpoint configuration, reference the configuration in the <`endpoint`> element for each endpoint as shown in the following sample.  
+ Once you've added the standard endpoint configuration, reference the configuration in the <`endpoint`> element for each endpoint as shown in the following sample.  
 
 ```xml  
 <services>  

@@ -4,7 +4,7 @@ description: Learn how to configure HTTP/HTTPS to allow WCF services and clients
 ms.date: "04/08/2019"
 helpviewer_keywords: 
   - "configuring HTTP [WCF]"
-ms.assetid: b0c29a86-bc0c-41b3-bc1e-4eb5bb5714d4
+ms.topic: how-to
 ---
 # Configuring HTTP and HTTPS
 

@@ -2,7 +2,7 @@
 description: "Learn more about: Configuring Internet Information Services 7.0 for Windows Communication Foundation"
 title: "Configuring Internet Information Services 7.0 for Windows Communication Foundation"
 ms.date: "03/30/2017"
-ms.assetid: 1050d395-092e-44d3-b4ba-66be3b039ffb
+ms.topic: how-to
 ---
 # Configuring Internet Information Services 7.0 for Windows Communication Foundation
 

@@ -2,11 +2,11 @@
 description: "Learn more about: Configuring Serialization in a Workflow Service"
 title: "Configuring Serialization in a Workflow Service"
 ms.date: "03/30/2017"
-ms.assetid: aa70b290-a2ee-4c3c-90ea-d0a7665096ae
+ms.topic: how-to
 ---
 # Configuring Serialization in a Workflow Service
 
-Workflow services are Windows Communication Foundation (WCF) services and so have the option of using either the <xref:System.Runtime.Serialization.DataContractSerializer> (the default) or the <xref:System.Xml.Serialization.XmlSerializer>. When writing non-workflow services the type of serializer to use is specified on the service or operation contract. When creating WCF workflow services you don’t specify these contracts in code, but rather they are generated at runtime by contract inference. For more information about contract inference, see  [Using Contracts in Workflow](using-contracts-in-workflow.md).  The serializer is specified using the <xref:System.ServiceModel.Activities.Receive.SerializerOption%2A> property. This can be set in the designer as shown in the following illustration.  
+Workflow services are Windows Communication Foundation (WCF) services and so have the option of using either the <xref:System.Runtime.Serialization.DataContractSerializer> (the default) or the <xref:System.Xml.Serialization.XmlSerializer>. When writing non-workflow services the type of serializer to use is specified on the service or operation contract. When creating WCF workflow services you don't specify these contracts in code, but rather they are generated at runtime by contract inference. For more information about contract inference, see  [Using Contracts in Workflow](using-contracts-in-workflow.md).  The serializer is specified using the <xref:System.ServiceModel.Activities.Receive.SerializerOption%2A> property. This can be set in the designer as shown in the following illustration.  
 
  ![Setting the SerializerOption property in the Properties Window.](./media/configuring-serialization-in-a-workflow-service/setting-serializer-property.png)  
 

@@ -6,7 +6,7 @@ helpviewer_keywords:
   - "Windows Communication Foundation [WCF], system-provided bindings"
   - "WCF [WCF], system-provided bindings"
   - "bindings [WCF], system-provided"
-ms.assetid: 443f8d65-f1f2-4311-83b3-4d8fdf7ccf16
+ms.topic: how-to
 ---
 # Configuring System-Provided Bindings
 

@@ -2,7 +2,7 @@
 description: "Learn more about: Configuring the Net.TCP Port Sharing Service"
 title: "Configuring the Net.TCP Port Sharing Service"
 ms.date: "03/30/2017"
-ms.assetid: b6dd81fa-68b7-4e1b-868e-88e5901b7ea0
+ms.topic: how-to
 ---
 # Configuring the Net.TCP Port Sharing Service
 

@@ -2,7 +2,7 @@
 description: "Learn more about: Configuring the Windows Process Activation Service for Use with Windows Communication Foundation"
 title: "Configuring the Windows Process Activation Service for Use with Windows Communication Foundation"
 ms.date: "03/30/2017"
-ms.assetid: 1d50712e-53cd-4773-b8bc-a1e1aad66b78
+ms.topic: how-to
 ---
 # Configuring the Windows Process Activation Service for Use with Windows Communication Foundation
 
@@ -50,7 +50,7 @@ appcmd.exe set site "Default Web Site" -+bindings.[protocol='net.tcp',bindingInf
 appcmd.exe set app "Default Web Site/appOne" /enabledProtocols:net.tcp  
 ```  
 
- The list of enabled protocols can also be set in the \<applicationDefaults> element of the site’s XML configuration stored in ApplicationHost.config.  
+ The list of enabled protocols can also be set in the \<applicationDefaults> element of the site's XML configuration stored in ApplicationHost.config.  
 
  The following XML code from applicationHost.config illustrates a site bound to both HTTP and non-HTTP protocols. The additional configuration required to support non-HTTP protocols is called out with comments.  
 

@@ -2,11 +2,11 @@
 title: "Configuring Timeout Values on a Binding"
 description: Learn how to manage timeout settings for WCF bindings to improve performance, usability, and security of your service.
 ms.date: "03/30/2017"
-ms.assetid: b5c825a2-b48f-444a-8659-61751ff11d34
+ms.topic: how-to
 ---
 # Configuring Timeout Values on a Binding
 
-There are a number of timeout settings available in WCF bindings. Setting these timeout settings correctly can improve not only your service’s performance but also play a role in the usability and security of your service. The following timeouts are available on WCF bindings:  
+There are a number of timeout settings available in WCF bindings. Setting these timeout settings correctly can improve not only your service's performance but also play a role in the usability and security of your service. The following timeouts are available on WCF bindings:  
 
 1. OpenTimeout  
 

@@ -2,7 +2,7 @@
 description: "Learn more about: Configuring WorkflowServiceHost"
 title: "Configuring WorkflowServiceHost"
 ms.date: "03/30/2017"
-ms.assetid: d8e961cb-0ef5-4f8c-8a25-e76ae6334fed
+ms.topic: how-to
 ---
 # Configuring WorkflowServiceHost
 

@@ -4,7 +4,7 @@ title: "Configuring WS-Atomic Transaction Support"
 ms.date: "03/30/2017"
 helpviewer_keywords:
   - "WS-AT protocol [WCF], configuring WS-Atomic Transaction"
-ms.assetid: cb9f1c9c-1439-4172-b9bc-b01c3e09ac48
+ms.topic: how-to
 ---
 # Configure WS-Atomic Transaction support
 
@@ -68,7 +68,7 @@ You must already possess the required certificates to establish trust. To learn
 
 1. On machine A, import the file representation of certB into the LocalMachine\MY and LocalMachine\ROOT stores. This declares that machine A trusts certB to communicate with it.
 
-2. On machine B, import certA’s file into the LocalMachine\MY and LocalMachine\ROOT stores. This implies that machine B trusts certA to communicate with it.
+2. On machine B, import certA's file into the LocalMachine\MY and LocalMachine\ROOT stores. This implies that machine B trusts certA to communicate with it.
 
 After completing these steps, trust is established between the two machines, and they can be configured to communicate with each other using WS-AT.
 
@@ -83,9 +83,9 @@ You can configure this by using the MMC WS-AT snap-in. For more information abou
 2. Configure machine B's settings. For "Endpoint Certificate", select certB. For "Authorized Certificates", select the certA.
 
 > [!NOTE]
-> When one machine sends a message to the other machine, the sender attempts to verify that the subject name of the recipient’s certificate and the name of the recipient’s machine match. If they do not match, certificate verification fails and the two machines cannot communicate.
+> When one machine sends a message to the other machine, the sender attempts to verify that the subject name of the recipient's certificate and the name of the recipient's machine match. If they do not match, certificate verification fails and the two machines cannot communicate.
 >
-> For a machine joined to a domain, the name is the fully qualified domain name. By default, the name of a machine on a workgroup is the machine’s NetBIOS name. However, the name can also include a Domain Name System (DNS) suffix if one is present for the connection being used between the two machines.
+> For a machine joined to a domain, the name is the fully qualified domain name. By default, the name of a machine on a workgroup is the machine's NetBIOS name. However, the name can also include a Domain Name System (DNS) suffix if one is present for the connection being used between the two machines.
 >
 > If the name of the machine changes, for example, when a workgroup machine joins a domain, you must reissue certificates or manually configure DNS suffixes.
 

@@ -2,7 +2,7 @@
 description: "Learn more about: How to: Create an AJAX-Enabled WCF Service and an ASP.NET Client that Accesses the Service"
 title: Create an AJAX-Enabled WCF Service and an ASP.NET Client in Visual Studio
 ms.date: 08/17/2018
-ms.assetid: 95012df8-2a66-420d-944a-8afab261013e
+ms.topic: how-to
 ---
 # How to: Create an AJAX-Enabled WCF Service and an ASP.NET Client that Accesses the Service
 

@@ -4,7 +4,7 @@ title: "Data Contract Schema Reference"
 ms.date: "03/30/2017"
 helpviewer_keywords:
   - "data contracts [WCF], schema reference"
-ms.assetid: 9ebb0ebe-8166-4c93-980a-7c8f1f38f7c0
+ms.topic: reference
 ---
 # Data Contract Schema Reference
 

@@ -2,7 +2,7 @@
 description: "Learn more about: Using a Custom Binding with the Discovery Client Channel"
 title: "Using a Custom Binding with the Discovery Client Channel"
 ms.date: "03/30/2017"
-ms.assetid: 36f95e75-04f7-44f3-a995-a0d623624d7f
+ms.topic: how-to
 ---
 # Using a Custom Binding with the Discovery Client Channel
 

@@ -2,7 +2,7 @@
 description: "Learn more about: Find Private Key Tool (FindPrivateKey.exe)"
 title: "Find Private Key Tool (FindPrivateKey.exe)"
 ms.date: "09/11/2017"
-ms.assetid: b8846a95-3fcc-4e8c-b9c0-128d975a6307
+ms.topic: reference
 ---
 # Find Private Key Tool (FindPrivateKey.exe)
 

@@ -2,7 +2,7 @@
 description: "Learn more about: Generating Data Type Classes from XML"
 title: "Generating Data Type Classes from XML"
 ms.date: "03/30/2017"
-ms.assetid: e4e5e4e8-527f-44d1-92fa-8904a08784ea
+ms.topic: how-to
 ---
 # Generating Data Type Classes from XML
 

@@ -5,7 +5,7 @@ ms.date: "03/30/2017"
 helpviewer_keywords:
   - "Windows Communication Foundation [WCF], glossary"
   - "WCF [WCF], glossary"
-ms.assetid: 39cd36f4-8a28-4d0b-a830-98d55c9d30ae
+ms.topic: reference
 ---
 
 # Windows Communication Foundation Glossary for .NET Framework 4.5

@@ -2,7 +2,7 @@
 description: "Learn more about: Interpreting Error Codes Returned by wsatConfig.exe"
 title: "Interpreting Error Codes Returned by wsatConfig.exe"
 ms.date: "03/30/2017"
-ms.assetid: ab65f22b-0d69-4c21-9aaf-74acef0ca102
+ms.topic: reference
 ---
 # Interpreting Error Codes Returned by wsatConfig.exe
 

@@ -2,7 +2,7 @@
 description: "Learn more about: Renaming a WCF Service"
 title: "Renaming a WCF Service"
 ms.date: "03/30/2017"
-ms.assetid: 14235a65-b1c5-409d-b6cc-a979acd54bbd
+ms.topic: how-to
 ---
 # Renaming a WCF Service