deps: Bump the wcf-client group with 4 updates - #257
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Conversation
Bumps System.ServiceModel.Federation from 4.10.3 to 10.0.652802 Bumps System.ServiceModel.Http from 4.10.3 to 10.0.652802 Bumps System.ServiceModel.NetTcp from 4.10.3 to 10.0.652802 Bumps System.ServiceModel.Primitives from 4.10.3 to 10.0.652802 --- updated-dependencies: - dependency-name: System.ServiceModel.Federation dependency-version: 10.0.652802 dependency-type: direct:production update-type: version-update:semver-major dependency-group: wcf-client - dependency-name: System.ServiceModel.Http dependency-version: 10.0.652802 dependency-type: direct:production update-type: version-update:semver-major dependency-group: wcf-client - dependency-name: System.ServiceModel.Primitives dependency-version: 10.0.652802 dependency-type: direct:production update-type: version-update:semver-major dependency-group: wcf-client - dependency-name: System.ServiceModel.NetTcp dependency-version: 10.0.652802 dependency-type: direct:production update-type: version-update:semver-major dependency-group: wcf-client ... Signed-off-by: dependabot[bot] <support@github.com>
This was referenced Aug 11, 2026
Contributor
Author
|
Looks like these dependencies are no longer being updated by Dependabot, so this is no longer needed. |
dependabot
Bot
deleted the
dependabot/nuget/Source/ISHRemote/Trisoft.ISHRemote/wcf-client-667ac883e7
branch
August 11, 2026 18:17
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Rebasing might not happen immediately, so don't worry if this takes some time.
Note: if you make any changes to this PR yourself, they will take precedence over the rebase.
Updated System.ServiceModel.Federation from 4.10.3 to 10.0.652802.
Release notes
Sourced from System.ServiceModel.Federation's releases.
10.0.0
What's Changed
Full Changelog: dotnet/wcf@v8.1.2-rtm...v10.0.0-rtm
8.1.2
What's Changed
Full Changelog: dotnet/wcf@v8.0.0-preview1-dotnet-svcutil...v8.1.2-rtm
8.1.1
Release Notes
Package Info
Bug Fixes
8.1
Release Notes
Package Info
What's New
Net standard 2.0 and .NET Framework support are back in WCF Client 8.1 Release.
Bug Fixes
New Contributors
Full Changelog: dotnet/wcf@v8.0.0-rtm...v8.1.0-rtm
8.0.0
Release Notes
Package Info
What's New
WCF Client 8.0 is the successor to WCF Client 6.0. It will be supported for three years as a long-term support (LTS) release, align with .NET 8.0.0.
Breaking Change:
https://learn.microsoft.com/en-us/dotnet/core/compatibility/wcf-client/8.0/configurationname-apis
8.0.0-preview1-dotnet-svcutil
Release Notes
dotnet-svcutil v8.0.0 preview1 was released on January 8th, 2025.
Packages
What's New
6.2
Release Notes
Package Info
What's New
We've added the System.ServiceModel.UnixDomainSocket package (PR #5172) to provide support for using unix domain sockets with WCF Client. This provides an alternative to NetNamedPipe and works on all supported platforms. This was contributed by @birojnayak from AWS.
Bug Fixes:
-Use LINQ Expressions for implementation of default IOperationInvoker. If there are any unexpected compatibility issues, the prior implementation can be used by setting the AppContext switch
System.ServiceModel.Dispatcher.UseLegacyInvokeDelegateto true, contributed by @g7ed6e (PR #5298).6.1
Release Notes
Package Info
What's New
6.0
Release Notes
Package Info
What's New
6.0.0-rc
Release Notes
Package Info
What's New
Previously when using Duplex contract, failure to capture synchronization context on channel factory open. The behavior now matches .NET framework, by default, we will now capture the synchronization context, and will dispatch callbacks to the captured context. To revert to 4.x behavior, apply the
CallbackBehaviorAttributewith theUseSynchronizationContextproperty set tofalse.See Also
Breaking changes doc
6.0.0-preview1
Release Notes
Package Info
What's New
WCF Client (used to be called WCF Core) 6.0 preview 1 release is the successor release to WCF Core 4.10. This release has added support for NetNamedPipe (Initial NetNamedPipe implementation #4955). This release also takes a step forward to align with the latest .NET LTS release and is moving to target .NET 6.0. WCF Client 6.0 does not target net standard 2.0.
In addition, System.ServiceModel.Duplex and System.ServiceModel.Security packages are deprecated, and this is the last release for these two Nuget packages. The types have been moved to System.ServiceModel.Primitives, these final packages will type forward the types to System.ServiceModel.Primitives for binary compatibility.
Recommended Action
See Also
Breaking changes doc
Commits viewable in compare view.
Updated System.ServiceModel.Http from 4.10.3 to 10.0.652802.
Release notes
Sourced from System.ServiceModel.Http's releases.
10.0.0
What's Changed
Full Changelog: dotnet/wcf@v8.1.2-rtm...v10.0.0-rtm
8.1.2
What's Changed
Full Changelog: dotnet/wcf@v8.0.0-preview1-dotnet-svcutil...v8.1.2-rtm
8.1.1
Release Notes
Package Info
Bug Fixes
8.1
Release Notes
Package Info
What's New
Net standard 2.0 and .NET Framework support are back in WCF Client 8.1 Release.
Bug Fixes
New Contributors
Full Changelog: dotnet/wcf@v8.0.0-rtm...v8.1.0-rtm
8.0.0
Release Notes
Package Info
What's New
WCF Client 8.0 is the successor to WCF Client 6.0. It will be supported for three years as a long-term support (LTS) release, align with .NET 8.0.0.
Breaking Change:
https://learn.microsoft.com/en-us/dotnet/core/compatibility/wcf-client/8.0/configurationname-apis
8.0.0-preview1-dotnet-svcutil
Release Notes
dotnet-svcutil v8.0.0 preview1 was released on January 8th, 2025.
Packages
What's New
6.2
Release Notes
Package Info
What's New
We've added the System.ServiceModel.UnixDomainSocket package (PR #5172) to provide support for using unix domain sockets with WCF Client. This provides an alternative to NetNamedPipe and works on all supported platforms. This was contributed by @birojnayak from AWS.
Bug Fixes:
-Use LINQ Expressions for implementation of default IOperationInvoker. If there are any unexpected compatibility issues, the prior implementation can be used by setting the AppContext switch
System.ServiceModel.Dispatcher.UseLegacyInvokeDelegateto true, contributed by @g7ed6e (PR #5298).6.1
Release Notes
Package Info
What's New
6.0
Release Notes
Package Info
What's New
6.0.0-rc
Release Notes
Package Info
What's New
Previously when using Duplex contract, failure to capture synchronization context on channel factory open. The behavior now matches .NET framework, by default, we will now capture the synchronization context, and will dispatch callbacks to the captured context. To revert to 4.x behavior, apply the
CallbackBehaviorAttributewith theUseSynchronizationContextproperty set tofalse.See Also
Breaking changes doc
6.0.0-preview1
Release Notes
Package Info
What's New
WCF Client (used to be called WCF Core) 6.0 preview 1 release is the successor release to WCF Core 4.10. This release has added support for NetNamedPipe (Initial NetNamedPipe implementation #4955). This release also takes a step forward to align with the latest .NET LTS release and is moving to target .NET 6.0. WCF Client 6.0 does not target net standard 2.0.
In addition, System.ServiceModel.Duplex and System.ServiceModel.Security packages are deprecated, and this is the last release for these two Nuget packages. The types have been moved to System.ServiceModel.Primitives, these final packages will type forward the types to System.ServiceModel.Primitives for binary compatibility.
Recommended Action
See Also
Breaking changes doc
Commits viewable in compare view.
Updated System.ServiceModel.NetTcp from 4.10.3 to 10.0.652802.
Release notes
Sourced from System.ServiceModel.NetTcp's releases.
10.0.0
What's Changed
Full Changelog: dotnet/wcf@v8.1.2-rtm...v10.0.0-rtm
8.1.2
What's Changed
Full Changelog: dotnet/wcf@v8.0.0-preview1-dotnet-svcutil...v8.1.2-rtm
8.1.1
Release Notes
Package Info
Bug Fixes
8.1
Release Notes
Package Info
What's New
Net standard 2.0 and .NET Framework support are back in WCF Client 8.1 Release.
Bug Fixes
New Contributors
Full Changelog: dotnet/wcf@v8.0.0-rtm...v8.1.0-rtm
8.0.0
Release Notes
Package Info
What's New
WCF Client 8.0 is the successor to WCF Client 6.0. It will be supported for three years as a long-term support (LTS) release, align with .NET 8.0.0.
Breaking Change:
https://learn.microsoft.com/en-us/dotnet/core/compatibility/wcf-client/8.0/configurationname-apis
8.0.0-preview1-dotnet-svcutil
Release Notes
dotnet-svcutil v8.0.0 preview1 was released on January 8th, 2025.
Packages
What's New
6.2
Release Notes
Package Info
What's New
We've added the System.ServiceModel.UnixDomainSocket package (PR #5172) to provide support for using unix domain sockets with WCF Client. This provides an alternative to NetNamedPipe and works on all supported platforms. This was contributed by @birojnayak from AWS.
Bug Fixes:
-Use LINQ Expressions for implementation of default IOperationInvoker. If there are any unexpected compatibility issues, the prior implementation can be used by setting the AppContext switch
System.ServiceModel.Dispatcher.UseLegacyInvokeDelegateto true, contributed by @g7ed6e (PR #5298).6.1
Release Notes
Package Info
What's New
6.0
Release Notes
Package Info
What's New
6.0.0-rc
Release Notes
Package Info
What's New
Previously when using Duplex contract, failure to capture synchronization context on channel factory open. The behavior now matches .NET framework, by default, we will now capture the synchronization context, and will dispatch callbacks to the captured context. To revert to 4.x behavior, apply the
CallbackBehaviorAttributewith theUseSynchronizationContextproperty set tofalse.See Also
Breaking changes doc
6.0.0-preview1
Release Notes
Package Info
What's New
WCF Client (used to be called WCF Core) 6.0 preview 1 release is the successor release to WCF Core 4.10. This release has added support for NetNamedPipe (Initial NetNamedPipe implementation #4955). This release also takes a step forward to align with the latest .NET LTS release and is moving to target .NET 6.0. WCF Client 6.0 does not target net standard 2.0.
In addition, System.ServiceModel.Duplex and System.ServiceModel.Security packages are deprecated, and this is the last release for these two Nuget packages. The types have been moved to System.ServiceModel.Primitives, these final packages will type forward the types to System.ServiceModel.Primitives for binary compatibility.
Recommended Action
See Also
Breaking changes doc
Commits viewable in compare view.
Updated System.ServiceModel.Primitives from 4.10.3 to 10.0.652802.
Release notes
Sourced from System.ServiceModel.Primitives's releases.
10.0.0
What's Changed
Full Changelog: dotnet/wcf@v8.1.2-rtm...v10.0.0-rtm
8.1.2
What's Changed
Full Changelog: dotnet/wcf@v8.0.0-preview1-dotnet-svcutil...v8.1.2-rtm
8.1.1
Release Notes
Package Info
Bug Fixes
8.1
Release Notes
Package Info
What's New
Net standard 2.0 and .NET Framework support are back in WCF Client 8.1 Release.
Description has been truncated