[Breaking change]: Removal of WCF api's with a configurationName parameter #43111
Labels
binary incompatible
Existing binaries may encounter a breaking change in behavior.
breaking-change
Indicates a .NET Core breaking change
doc-idea
Indicates issues that are suggestions for new topics [org][type][category]
Pri1
High priority, do before Pri2 and Pri3
source incompatible
Source code may encounter a breaking change in behavior when targeting the new version.
⌚ Not Triaged
Not triaged
Description
The WCF api's which accept either a
configurationName
parameter or anendpointConfigurationName
parameter were used in .NET Framework to load client configuration parameters such as theBinding
configuration, and theEndpointAddress
details. These api's have been removed.Version
.NET 8 GA
Previous behavior
The removed api's were previously suppressed from Intellisense suggestions. Using any of the removed api's would result in a
PlatformNotSupportedException
being thrown.New behavior
The api's no longer exist.
Type of breaking change
Reason for change
These api's were not implemented on .NET and any calls to these api's would result in an exception.
Recommended action
Remove any usage of these api's. If you are using a WCF client generated by the svcutil utility from the .NET Framework SDK, the generated client will have constructors which call base class constructors that have been removed. The base class will be either
ClientBase<TChannel>
orDuplexClientBase<TChannel>
. The generated constructors were unusable on .NET as they would have resulted in aPlatformNotSupportedException
being thrown. If you are multi-targeting .NET Framework and .NET and are still using these generated constructors on .NET Framework, usage will need to be conditionally compiled. If you are not using these constructors, you can delete them from the generated code. Alternatively, consider regenerating the client using dotnet-svcutil.Feature area
WCF Client
Affected APIs
The text was updated successfully, but these errors were encountered: