Update ms.topic for framework/wcf and framework/whats-new (#24230)

Author: tdykstra

docfx.json

@@ -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",

docs/framework/wcf/extending/specifying-a-custom-crypto-algorithm.md

@@ -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>  

docs/framework/wcf/extending/walkthrough-creating-custom-client-and-service-credentials.md

@@ -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
 

docs/framework/wcf/extending/ws-metadataexchange-bindings.md

@@ -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
 

docs/framework/wcf/feature-details/client-configuration.md

@@ -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
 

docs/framework/wcf/feature-details/config-wcf-service-with-aspnet-web-service.md

@@ -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
 

docs/framework/wcf/feature-details/configuring-discovery-in-a-configuration-file.md

@@ -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>  

docs/framework/wcf/feature-details/configuring-http-and-https.md

@@ -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
 

docs/framework/wcf/feature-details/configuring-iis-for-wcf.md

@@ -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
 

docs/framework/wcf/feature-details/configuring-serialization-in-a-workflow-service.md

@@ -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)