WCF APIs removed

Author: gewarren

docs/core/compatibility/8.0.md

@@ -155,6 +155,12 @@ If you're migrating an app to .NET 8, the breaking changes listed here might aff
 | [PublishedTrimmed projects fail reflection-based serialization](serialization/8.0/publishtrimmed.md) | Behavioral change |
 | [Reflection-based deserializer resolves metadata eagerly](serialization/8.0/metadata-resolving.md) | Behavioral change |
 
+## WCF client
+
+| Title                                                                                                | Type of change             |
+|------------------------------------------------------------------------------------------------------|----------------------------|
+| [Removal of WCF APIs with a `configurationName` parameter](wcf-client/8.0/configurationname-apis.md) | Source/binary incompatible |
+
 ## Windows Forms
 
 | Title                                                                                                    | Type of change      |

docs/core/compatibility/toc.yml

@@ -326,6 +326,10 @@ items:
                 href: serialization/8.0/publishtrimmed.md
               - name: Reflection-based deserializer resolves metadata eagerly
                 href: serialization/8.0/metadata-resolving.md
+          - name: WCF client
+            items:
+              - name: Removal of WCF APIs with a `configurationName` parameter
+                href: wcf-client/8.0/configurationname-apis.md
           - name: Windows Forms
             items:
               - name: Anchor layout changes
@@ -1982,6 +1986,10 @@ items:
             href: visualbasic.md
       - name: WCF Client
         items:
+          - name: .NET 8
+            items:
+              - name: Removal of WCF APIs with a `configurationName` parameter
+                href: wcf-client/8.0/configurationname-apis.md
           - name: "6.0"
             items:
               - name: .NET Standard 2.0 no longer supported

docs/core/compatibility/wcf-client/8.0/configurationname-apis.md

@@ -0,0 +1,52 @@
+---
+title: "Removal of WCF APIs with a `configurationName` parameter"
+description: Learn about the breaking change in .NET 8 where the WCF APIs that accept a `configurationName` parameter have been removed.
+ms.date: 11/13/2024
+ai-usage: ai-assisted
+ms.custom: https://github.com/dotnet/docs/issues/43111
+---
+
+# Removal of WCF APIs with a `configurationName` parameter
+
+The WCF APIs that accept either a `configurationName` parameter or an `endpointConfigurationName` parameter have been removed in .NET 8. These APIs were previously used in .NET Framework to load client configuration parameters such as the `Binding` configuration and the `EndpointAddress` details.
+
+## Version introduced
+
+.NET 8 GA
+
+## Previous behavior
+
+The removed APIs were previously suppressed from IntelliSense suggestions. Using any of the removed APIs resulted in a <xref:System.PlatformNotSupportedException> being thrown.
+
+## New behavior
+
+The APIs no longer exist. If you upgrade to .NET 8 and recompile your code, it will fail.
+
+## Type of breaking change
+
+This change is a [binary incompatible](../categories.md#binary-incompatible) and [source incompatible](../categories.md#source-incompatible) change.
+
+## Reason for change
+
+These APIs were never implemented on .NET and any calls to these APIs previously resulted in a run-time exception.
+
+## Recommended action
+
+Remove any usage of these APIs.
+
+If you're using a WCF client generated by the `svcutil` utility from the .NET Framework SDK, the generated client will have constructors that call base class constructors that have been removed. The base class will be either <xref:System.ServiceModel.ClientBase`1> or <xref:System.ServiceModel.DuplexClientBase`1>. The generated constructors were unusable on .NET as they resulted in a `PlatformNotSupportedException` being thrown.
+
+- If you're multi-targeting .NET Framework and .NET and are still using these generated constructors on .NET Framework, you'll need to conditionally compile their usage.
+- If you're not using these constructors, you can delete them from the generated code. Alternatively, consider regenerating the client using `dotnet-svcutil`.
+
+## Affected APIs
+
+- <xref:System.ServiceModel.NetHttpBinding.%23ctor(System.String)>
+- <xref:System.ServiceModel.NetTcpBinding.%23ctor(System.String)>
+- <xref:System.ServiceModel.ChannelFactory.ApplyConfiguration(System.String)?displayProperty=fullName>
+- <xref:System.ServiceModel.ChannelFactory.InitializeEndpoint(System.String,System.ServiceModel.EndpointAddress)?displayProperty=fullName>
+- <xref:System.ServiceModel.ChannelFactory`1.%23ctor(System.String)>
+- <xref:System.ServiceModel.ChannelFactory`1.%23ctor(System.String,System.ServiceModel.EndpointAddress)><xref:System.ServiceModel.DuplexChannelFactory`1.%23ctor(System.ServiceModel.InstanceContext,System.String)>
+- <xref:System.ServiceModel.DuplexChannelFactory`1.%23ctor(System.ServiceModel.InstanceContext,System.String,System.ServiceModel.EndpointAddress)><xref:System.ServiceModel.DuplexClientBase`1.%23ctor(System.ServiceModel.InstanceContext,System.String)>
+- <xref:System.ServiceModel.DuplexClientBase`1.%23ctor(System.ServiceModel.InstanceContext,System.String,System.ServiceModel.EndpointAddress)>
+- <xref:System.ServiceModel.DuplexClientBase`1.%23ctor(System.ServiceModel.InstanceContext,System.String,System.String)>