Update the WCF packages to the latest version that is compatible with v4.10.3 #26406
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Summary
Fix #19238
PackageReferenceitems that were commented out.10.0.0-rc.2.final.The
10.0.0-rc.2.finalversionServiceModelpackages are backward compatible:The packages
System.ServiceModel.Duplex,System.ServiceModel.Security, andSystem.Private.ServiceModelare discontinued.The package
System.ServiceModel.Primitivesships 3 facade assembliesSystem.ServiceModel.dllSystem.ServiceModel.Duplex.dllSystem.ServiceModel.Security.dllThe package
System.Private.ServiceModelis no longer needed, as every package now carries its own implementation.I have verified that the
ActiveDirectorymodule can be correctly imported with in PowerShell built with the10.0.0-rc.2.finalWCF packages.Before this change, the
*ServiceModel*assemblies carried by PowerShell are:After this change, the
*ServiceModel*assemblies carried by PowerShell are:The difference of Before vs. After is shown below. The
System.Private.ServiceModel.dllis no longer needed with the latest version, and theSystem.ServiceModel.NetFramingBase.dllis a new dependency of theSystem.ServiceModel.NetTcp.dll.