Release Notes

Package Info

CoreWCF.ConfigurationManager 1.9.0
CoreWCF.Http 1.9.0
CoreWCF.Kafka 1.9.0
CoreWCF.Kafka.Client 1.9.0
CoreWCF.MSMQ 1.9.0
CoreWCF.NetFramingBase 1.9.0
CoreWCF.NetNamedPipe 1.9.0
CoreWCF.NetTcp 1.9.0
CoreWCF.Primitives 1.9.0
CoreWCF.Queue 1.9.0
CoreWCF.RabbitMQ 1.9.0
CoreWCF.RabbitMQ.Client 1.9.0
CoreWCF.Templates 1.9.0
CoreWCF.UnixDomainSocket 1.9.0
CoreWCF.WebHttp 1.9.0

.NET Compatibility

This release depends on .NET Standard 2.0 and runs on any .NET version which supports .NET Standard 2.0. This release supports .NET Framework 4.6.2 and above, .NET 8, .NET 9, and .NET 10. It is built on top of ASP.NET Core and has been tested and runs on all currently supported versions of ASP.NET Core up to 10.0. The CoreWCF.RabbitMQ.Client, CoreWCF.Kafka.Client, and CoreWCF.UnixDomainSocket packages only support .NET 8 or later.

New Features

A service using NetNamedPipe can now listen from inside an Application Container and be connected to by a WCF client from outside the application container.

What's Changed

• Provide opt-out switch for EnableCoreWCFOperationInvokerGenerator attribute by @mconnew in #1706
• Reduce CoreWCF.BuildTools analyzer and source generator IDE performance overhead by @Copilot in #1689
• Move named pipe to RTM by @mconnew in #1697
• Add support for NetNamedPipe listening inside a Win32 App Container by @mconnew in #1693
• Make operation invoker generator enabled by default with graceful fallback by @Copilot in #1660
• Annotate WebApplicationExtensions with ExcludeFromCodeCoverage by @Copilot in #1658
• Update the expected *.wsdl's for net10.0+ to include dateOnly/timeOnly by @StephenMolloy in #1654
• Add ServiceBehaviorAttribute.EnsureOrderedDispatch property by @Copilot in #1645

Bug Fixes

• Eliminate HttpDateParse by @mconnew in #1705
• Update the Negotiate implementation for .NET 8+ compatibility by @nmangue in #1575
• Fix adding HttpContext to message properties before potential Message disposal by @mconnew in #1691
• Fix authorization policy support for class-based service contracts by @Copilot in #1661
• Fix analyzer packaging path to match Roslyn 4.8 dependency by @Copilot in #1662
• Fix nullable reference type mismatch in operation invoker key generation by @Copilot in #1659
• Fixing WSDL generation for NetNamedPipe by @mconnew in #1637

Feedback

Your feedback is important and appreciated. Please use the discussion #1709 for your questions and comments.

New Contributors

• StephenMolloy made their first contribution in #1654

Full Changelog: v1.8.0...v1.9.0

Release Notes

Package Info

CoreWCF.ConfigurationManager 1.8.1
CoreWCF.Http 1.8.1
CoreWCF.Kafka 1.8.1
CoreWCF.Kafka.Client 1.8.1
CoreWCF.MSMQ 1.8.1
CoreWCF.NetFramingBase 1.8.1
CoreWCF.NetNamedPipe 1.8.1-preview.1
CoreWCF.NetTcp 1.8.1
CoreWCF.Primitives 1.8.1
CoreWCF.Queue 1.8.1
CoreWCF.RabbitMQ 1.8.1
CoreWCF.RabbitMQ.Client 1.8.1
CoreWCF.Templates 1.8.1
CoreWCF.UnixDomainSocket 1.8.1
CoreWCF.WebHttp 1.8.1

.NET Compatibility

This release depends on .NET Standard 2.0 and runs on any .NET version which supports .NET Standard 2.0. This release supports .NET Framework 4.6.2 and above, .NET 8, and .NET 9. It has also been tested against .NET 10 and there are currently no known issues. It is built on top of ASP.NET Core and has been tested and runs on all currently supported versions of ASP.NET Core up to 9.0. The CoreWCF.RabbitMQ.Client, CoreWCF.Kafka.Client, and CoreWCF.UnixDomainSocket packages only support .NET 8 or later.

What's Changed

Security Fixes

This is a servicing release that addresses multiple security vulnerabilities. For full details, affected versions, and recommended mitigations, see each advisory linked below.

• CVE-2026-54782 / GHSA-xjr9-gg9q-jx3v — Authentication bypass in CoreWCF SAML 1.1 / 2.0 token signature validation
• CVE-2026-54774 / GHSA-rpj7-hr7h-w6p9 — SamlSerializer skips SignatureValue verification when SAML signing token is not an X.509 certificate
• CVE-2026-54781 / GHSA-48pq-2xq3-c2m4 — SAML SubjectConfirmation methods and holder-of-key proof keys are not enforced
• CVE-2026-54779 / GHSA-9jr3-rj99-8jq3 — SAML token replay protection is inoperative
• CVE-2026-54780 / GHSA-4v55-cpmv-3vcm — WS-Security Reference DigestMethod Algorithm-Suite Bypass
• CVE-2026-54773 / GHSA-jc6x-rj79-w4mx — WS-Security signature substitution via document-wide Signature lookup
• CVE-2026-54783 / GHSA-gqv6-pwcg-87r8 — XML Signature Wrapping in WS-Security endorsing/supporting signature verification allows replay of captured signed messages
• CVE-2026-54772 / GHSA-p86g-xrr2-pf7c — Pre-authentication infinite-loop CPU exhaustion in CoreWCF net.tcp / net.pipe / net.uds framing handshake
• CVE-2026-54777 / GHSA-6jj2-4q5c-x8g6 — CoreWCF NetNamedPipe transport accepts attach to a pre-existing named pipe instance
• CVE-2026-54776 / GHSA-wjpq-6766-7f5j — Unix Domain Socket PosixIdentity transport accepts connections that skip the security upgrade
• CVE-2026-54778 / GHSA-q6v9-43v5-jv9q — UnixDomainSocket Non-Reentrant POSIX Identity Resolution
• CVE-2026-54775 / GHSA-m744-jhq9-ppw6 — Kafka consume pump halts permanently on a Kafka tombstone (null-value record), causing persistent endpoint denial of service

Feedback

Your feedback is important and appreciated. Please use the discussion #1738 for your questions and comments.

Full Changelog: v1.8.0...v1.8.1

Release Notes

Package Info

CoreWCF.ConfigurationManager 1.8.0
CoreWCF.Http 1.8.0
CoreWCF.Kafka 1.8.0
CoreWCF.Kafka.Client 1.8.0
CoreWCF.MSMQ 1.8.0
CoreWCF.NetFramingBase 1.8.0
CoreWCF.NetNamedPipe 1.8.0-preview.38
CoreWCF.NetTcp 1.8.0
CoreWCF.Primitives 1.8.0
CoreWCF.Queue 1.8.0
CoreWCF.RabbitMQ 1.8.0
CoreWCF.RabbitMQ.Client 1.8.0
CoreWCF.Templates 1.8.0
CoreWCF.UnixDomainSocket 1.8.0
CoreWCF.WebHttp 1.8.0

.NET Compatibility

This release depends on .NET Standard 2.0 and runs on any .NET version which supports .NET Standard 2.0. This release supports .NET Framework 4.6.2 and above, .NET 8, and .NET 9. It has also been tested against .NET 10 preview release and there are currently no known issues. It is built on top of ASP.NET Core and has been tested and runs on all currently supported versions of ASP.NET Core up to 9.0. The CoreWCF.RabbitMQ.Client, CoreWCF.Kafka.Client, and CoreWCF.UnixDomainSocket packages only support .NET 8 or later.

New Features

• Updating SamlSerializer to support SecurityTokenReference by @mconnew in #1625
• Added initial Opentelemetry support by @stefannikolei in #1512

What's Changed

• Updating package dependencies ready for 1.8 release by @mconnew in #1627
• Fix xunit build warnings by converting blocking task operations to async/await by @Copilot in #1618

Bug Fixes

• Downgrade Microsoft.CodeAnalysis.CSharp to 4.8.0 to remove warning when using .NET 8 SDK by @mconnew in #1548
• Fix CoreWCF.machine.config not being included in dotnet publish for transitive dependencies by @Copilot and @mconnew in #1621
• Handle dispatch exceptions and return appropriate Fault message by @afifi-ins in #1609
• Fix ChannelHandler null MessageVersion and add Unit Test by @afifi-ins in #1605
• Return bad request instead of throwing null reference exception (#701) by @fremo917 in #1599
• Fix non-structured log records by @MaceWindu in #1601
• Fix SendFaultAsync causing an InvalidOperationException as the prior read hadn't been advanced by @mconnew in #1600
• Prevent unhandled exceptions during service shutdown which can kill a process by @mconnew in #1597
• Fix use of AuthorizeRole attribute when service implementation has a base type by @mconnew in #1596
• Add more asynchronism to SecurityAppliedMessage.OnWriteMessageAsync by @g7ed6e in #1585
• Increase MaxRequestBodySize to match MaxReceivedMessageSize by @g7ed6e in #1593
• Fix TransferMode.Streamed for BasicHttpBinding with TransportWithMessageCredential by @VitezslavImrysek in #1583
• Fix ReplyChannelDispatcherTask is Null with NetHttpBinding by @afifi-ins in #1558
• Fix Context.User not being set in HandleRequest when using default authentication scheme by @afifi-ins in #1552
• Show problematic service type in exception message when type is not registered and does not have default constructor by @Copilot and @mconnew in #1606

Potential breaking changes

We take breaking changes very seriously and avoid them whenever possible. There have been a few small mistakes in the code base which we're now cleaning up. There were some types which were made public which shouldn't have been. They are internal implementation details and there shouldn't be any need to use them in your code base. If it turns out you were, please open an issue and we'll do a quick turnaround to expose them again. There were a couple of types which were in the wrong namespace. Where possible, we've left the original type but applied the Obsolete attribute if your code would continue to work with no code changes. We weren't able to do that in all cases, for example MessagePropertyAttribute was in the wrong namespace and we couldn't support using the original namespace. Here is the list of all the changes we've made where there have been api changes.

• Make SecureConversationDictionary and derived types internal by @g7ed6e in #1602
• Make XmlAttributeHolder internal by @g7ed6e in #1594
• Move SamlSerializer to correct namespace - original is marked [Obsolete] but is still functional by @g7ed6e in #1591
• Move MessagePropertyAttribute to correct namespace by @g7ed6e in #1592

Feedback

Your feedback is important and appreciated. Please use the discussion #1628 for your questions and comments.

New Contributors

• @fremo917 made their first contribution in #1599
• @MaceWindu made their first contribution in #1601
• @VitezslavImrysek made their first contribution in #1583

Full Changelog: v1.7.0...v1.8.0

Release Notes

Package Info

CoreWCF.ConfigurationManager 1.7.0
CoreWCF.Http 1.7.0
CoreWCF.Kafka 1.7.0
CoreWCF.Kafka.Client 1.7.0
CoreWCF.MSMQ 1.7.0
CoreWCF.NetFramingBase 1.7.0
CoreWCF.NetNamedPipe 1.7.0-preview
CoreWCF.NetTcp 1.7.0
CoreWCF.Primitives 1.7.0
CoreWCF.Queue 1.7.0
CoreWCF.RabbitMQ 1.7.0
CoreWCF.RabbitMQ.Client 1.7.0
CoreWCF.Templates 1.7.0
CoreWCF.UnixDomainSocket 1.7.0
CoreWCF.WebHttp 1.7.0

.NET Compatibility

This release depends on .NET Standard 2.0 and runs on any .NET version which supports .NET Standard 2.0. This release supports .NET Framework 4.6.2 and above, .NET 8, and .NET 9. It is built on top of ASP.NET Core and has been tested and runs on all currently supported versions of ASP.NET Core up to 9.0. The CoreWCF.RabbitMQ.Client, CoreWCF.Kafka.Client, and CoreWCF.UnixDomainSocket packages only support .NET 8 or later.

New Features

• Add WS2007HttpBinding and Unit Tests by @afifi-ins in #1479
• CoreWCF logo artifacts and psd by @ChrisMcKee in #1449

Many thanks to @ChrisMcKee for contributing our new logo. We've added it to our nuget packages as well as the nuget account, as well as the GitHub CoreWCF organization.

What's Changed

• Updated analyzers markdown file to reflect category change by @mconnew in #1541 and #1528
• Updated dependencies to minimum 8.0 versions release by @mconnew in #1540
• Replace BinaryFormatter with DataContractSerializer on .NET 9 by @g7ed6e in #1457
• Use Assert.Fail instead of true/false to fail the test by @Havunen in #1454
• Add net9.0 to UT and templates tfm by @g7ed6e in #1452
• Use IServiceProviderIsService to probe BI by @g7ed6e in #1453

Bug Fixes

• Extend the range of exceptions that are converted on an IO exception for NetTcp by @mconnew in #1538
• Add missing nuspec props by @g7ed6e in #1526
• Fix AuthorizeRoleAttribute use on methods in inherited contract interfaces by @mconnew in #1517
• Default value for AutoDisposeParameters should be true by @SaxoAnders in #1464
• Fix issue with implicit metadata Https url using the Http base address by @mconnew in #1524
• Use async IO to write MTOM XOP includes in responses by @MarcWils in #1495
• Place LICENSE in the root of the package to create valid NuGet packages by @MarcWils in #1499
• Fix writing of Disco Result by @stefannikolei in #1514
• Fixes DCJS serialization to use EmitTypeInformation.AsNeeded by @mconnew in #1497
• Fix buffer not being returned to pool by @SaxoAnders in #1462

Feedback

Your feedback is important and appreciated. Please use the discussion #1543 for your questions and comments.

New Contributors

• MarcWils made their first contribution in #1495
• stefannikolei made their first contribution in #1514
• Havunen made their first contribution in #1454
• ChrisMcKee made their first contribution in #1449

Full Changelog: v1.6.0...v1.7.0

Release Notes

Package Info

CoreWCF.ConfigurationManager 1.6.0
CoreWCF.Http 1.6.0
CoreWCF.Kafka 1.6.0
CoreWCF.Kafka.Client 1.6.0
CoreWCF.NetFramingBase 1.6.0
CoreWCF.NetTcp 1.6.0
CoreWCF.Primitives 1.6.0
CoreWCF.Queue 1.6.0
CoreWCF.RabbitMQ 1.6.0
CoreWCF.RabbitMQ.Client 1.6.0
CoreWCF.Templates 1.6.0
CoreWCF.UnixDomainSocket 1.6.0
CoreWCF.WebHttp 1.6.0

.NET Compatibility

This release depends on .NET Standard 2.0 and runs on any .NET version which supports .NET Standard 2.0. This release supports .NET Framework 4.6.2 and above, .NET 6, and .NET 8. It is built on top of ASP.NET Core and has been tested and runs on all currently supported versions of ASP.NET Core up to 8.0. The CoreWCF.RabbitMQ.Client, CoreWCF.Kafka.Client, and CoreWCF.UnixDomainSocket packages only support .NET 6 or later. Support for .NET 7 has been dropped as it is now out of support.

New Features

OperationContract initiating and terminating support

The OperationContractAttribute properties IsInitiating and IsTerminating have been made available by @afifi-ins in #1332

Support for injecting ServiceBehavior by service type

You can now inject a service behavior into DI to be applied to a single service type. This was added by @g7ed6e in #1040. You can read more about this in the blog post published here.

Support for injecting message properties into operation implementation

Using operation injection support, you can now automatically inject a message property into your service operation. This was added by @g7ed6e in #1286. You can read more about this in the blog post published here. We did make a couple of minor binary breaking changes with this feature, but you shouldn't see any compilation breaks. We changed some static Name properties on message property types to be const string. Static properties can't be used as values for attribute properties whereas constants can. For example, HttpRequestMessagePropert.Name used to be declared as public static string Name { get; }, and now is declared as public const string Name;. While this doesn't break compilation, it isn't binary compatible.

CoreWCF project template improvements

• Add IISExpress launch profile in templates by @g7ed6e in #1190
• Dropped net7.0 from templates by @g7ed6e in #1418

IOperationInvoker code generation

As part of an eventual goal to support aot for CoreWCF, we have introduced a code generator for implementing the default IOperationInvoker. This is an opt-in feature which you enable by setting the following in your project:

  <PropertyGroup>
    <EnableCoreWCFOperationInvokerGenerator>true</EnableCoreWCFOperationInvokerGenerator>
  </PropertyGroup>

This isn't sufficient to enable aot as we have other code which requires use of Ref.Emit, but is a step towards that goal.

New NetTcp configuration api's

As part of creating the full fix for GHSA-32jq-mv89-5rx7, the mechanism to configure some of the properties for NetTcp needed to be updated. You can read more about this in the blog post published here. Existing api's will continue to work so there shouldn't be any breaking changes for existing code.

What's Changed

Dependency updates

As part of the work to support keyed service dependency injection, we needed to update a few package dependencies to the .NET 8.0 versions. We run all our tests on .NET Framework 4.7.2 and .NET 6.0 so don't expect this to cause problems. If you do experience any issues due to CoreWCF upgrading dependencies, please open an issue explaining the error you're experiencing. The dependencies which were updated to 8.x versions are:

• Microsoft.Bcl.AsyncInterfaces
• Microsoft.Extensions.DependencyInjection
• Microsoft.Extensions.DependencyInjection.Abstractions
• Microsoft.Extensions.Primitives
  In addition, some other packages including some logging packages were updated from 2.x/4.x versions to 6.x versions. This was due to incompatibilities between the ASP.NET Core 2.1 version of Kestrel (as used with .NET Framework) and Microsoft.Extensions.Primitives which broke logging. Updating the logging packages to 6.x fixes this and is compatible with Kestrel 2.1, later versions of Kestrel shipped with the runtime, and the later Microsoft.Extensions.Primitives package.

Bug Fixes

• Add KafkaMessageProperty by @g7ed6e in #1277
• Prevent null reference exception when a client makes request to wrong endpoint address (#1331) by @bjornbouetsmith in #1335
• Detect kafka client side timeout by @g7ed6e in #1287
• Add support for binding namespace for WCF xml based configs by @VitahaPo in #1359
• Fix service endpoint URL in WSDL for WCF deployed in container by @VitahaPo in #1358
• Include CoreWCFWebApplicationExtensions.cs only within c# projects by @g7ed6e in #1371
• Fix NetFramingBase based transport Abort code path by @mconnew in #1348
• Fixed operation invoker expression based implementation to handle omitted primitive values by @g7ed6e in #1386
• Add multiple Kafka topic subscription using regex support by @g7ed6e in #1290
• Enabled MessageCredentialType.IssuedToken for WSHttpBinding by @emre-toraman in #1324
• Fix WSDL endpoint URLs for multiple services by @a-tze in #1409
• Remove NegotiateInputLengthDecider from CoreWCF.NetFramingBase which broke large messages by @SaxoAnders in #1424
• Make public CustomUserNameSecurityTokenAuthenticator by @lucashigor in #1419
• Add missing UDS ProtectionLevel property by @mconnew in #1433
• Add missing api's to DataContractSerializerOperationBehavior to enable configuring a resolver and/or surrogate provider by @imcarolwang in #1428
• Fix ByteStreamMessage behavior when calling CreateBufferedCopy and GetReaderAtBodyContents by @mconnew in #1436
• Fix multiple problems with listen uri being propagated when building dispatcher pipeline by @mconnew in #1435
• Add keyed services injection support in source gen by @g7ed6e in #1443

Feedback

Your feedback is important and appreciated. Please use the discussion #1447 for your questions and comments.

New Contributors

• @bjornbouetsmith made their first contribution in #1335
• @VitahaPo made their first contribution in #1359
• @emre-toraman made their first contribution in #1324
• @a-tze made their first contribution in #1409
• @241 made their first contribution in #1420
• @SaxoAnders made their first contribution in #1424
• @lucashigor made their first contribution in #1419

Full Changelog: v1.5.2...v1.6.0

Release Notes

Package Info

CoreWCF.ConfigurationManager 1.5.2
CoreWCF.Http 1.5.2
CoreWCF.Kafka 1.5.2
CoreWCF.Kafka.Client 1.5.2
CoreWCF.NetFramingBase 1.5.2
CoreWCF.NetTcp 1.5.2
CoreWCF.Primitives 1.5.2
CoreWCF.Queue 1.5.2
CoreWCF.RabbitMQ 1.5.2
CoreWCF.RabbitMQ.Client 1.5.2
CoreWCF.Templates 1.5.2
CoreWCF.UnixDomainSocket 1.5.2
CoreWCF.WebHttp 1.5.2

.NET Compatibility

This release depends on .NET Standard 2.0 and runs on any .NET version which supports .NET Standard 2.0. This release supports .NET Framework 4.6.2 and above, .NET 6, .NET 7, and .NET8. It is built on top of ASP.NET Core and has been tested and runs on all currently supported versions of ASP.NET Core up to 8.0. The CoreWCF.RabbitMQ.Client, CoreWCF.Kafka.Client, and CoreWCF.UnixDomainSocket packages only support .NET 6 or later.

What's Changed

Security Fixes

GHSA-32jq-mv89-5rx7 - CoreWCF NetFraming based services can leave connections open when they should be closed.

Feedback

Your feedback is important and appreciated. Please use the discussion #1288 for your questions and comments.

Full Changelog: v1.5.1...v1.5.2

Release Notes

Package Info

CoreWCF.ConfigurationManager 1.5.1
CoreWCF.Http 1.5.1
CoreWCF.Kafka 1.5.1
CoreWCF.Kafka.Client 1.5.1
CoreWCF.NetFramingBase 1.5.1
CoreWCF.NetTcp 1.5.1
CoreWCF.Primitives 1.5.1
CoreWCF.Queue 1.5.1
CoreWCF.RabbitMQ 1.5.1
CoreWCF.RabbitMQ.Client 1.5.1
CoreWCF.Templates 1.5.1
CoreWCF.UnixDomainSocket 1.5.1
CoreWCF.WebHttp 1.5.1

.NET Compatibility

This release depends on .NET Standard 2.0 and runs on any .NET version which supports .NET Standard 2.0. This release supports .NET Framework 4.6.2 and above, .NET 6, .NET 7, and .NET8. It is built on top of ASP.NET Core and has been tested and runs on all currently supported versions of ASP.NET Core up to 8.0. The CoreWCF.RabbitMQ.Client, CoreWCF.Kafka.Client, and CoreWCF.UnixDomainSocket packages only support .NET 6 or later.

New Features

Unix Domain Socket support

With this release, the CoreWCF.UnixDomainSocket package has come out of preview. This package enables you to use unix domain sockets for same host communication with CoreWCF. This provides an alternative to NetNamedPipe and works on all supported platforms. This was contributed by @birojnayak from AWS. The WCF Client project is simultaneously releasing the package System.ServiceModel.UnixDomainSocket to provide the client for this transport.

New implementation of default IOperationInvoker

In previous versions, the IOperationInvoker called MethodInfo.Invoke to call the service method. This is a relatively expensive way to call a method. In this release, we have a new implementation using LINQ Expressions which compiles a strongly typed lambda function to call the service method. This will provide a small performance improvement when dispatching a service call. If you experience any compatibility issues, you can set the AppContext switch CoreWCF.Dispatcher.UseLegacyInvokeDelegate to true to fallback to the previous implementation. If you need to do this, please open an issue explaining the problem you had. This feature was implemented by @g7ed6e
 

What's Changed

Bug Fixes

• Fix ambiguous UseServiceModel when using WebApplication by source including CoreWCF extension method for net6.0+ by @g7ed6e in #1235
• Fix PathTooLongException in OperationParameterInjectorGenerator by @g7ed6e in #1240
• For the Kafka binding, enhance offset commit handling when using AtLeastOnce semantic by @g7ed6e #1260
• Renamed UnixDomainSocketClientCredentialType.IdentityOnly to PosixIdentity and added enum type UnixDomainSocketSecurityMode to create UDS security mode TransportCredentialOnly to correctly reflect that PosixIdentity doesn't provide any transport encryption or integrity by @birojnayak in #1262
• Updated package dependencies to latest minor version by @mconnew in #1272
• Prevent code analyzers from analyzing CoreWCF extension method source included by package by @bjornen77 in #1278
• Prevent CoreWCF extension method source being included when targeting netstandard2.0 by @mconnew in #1196
• Prevent CoreWCF extension source file being compiled when project doesn't reference asp.net core by @mconnew in #1282

Feedback

Your feedback is important and appreciated. Please use the discussion #1288 for your questions and comments.

Full Changelog: v1.5.0-preview1...v1.5.1

Release Notes

Package Info

CoreWCF.ConfigurationManager 1.4.2
CoreWCF.Http 1.4.2
CoreWCF.Kafka 1.4.2
CoreWCF.Kafka.Client 1.4.2
CoreWCF.NetFramingBase 1.4.2
CoreWCF.NetTcp 1.4.2
CoreWCF.Primitives 1.4.2
CoreWCF.Queue 1.4.2
CoreWCF.RabbitMQ 1.4.2
CoreWCF.RabbitMQ.Client 1.4.2
CoreWCF.Templates 1.4.2
CoreWCF.WebHttp 1.4.2

.NET Compatibility

This release depends on .NET Standard 2.0 and runs on any .NET version which supports .NET Standard 2.0. This release supports .NET Framework 4.6.2 and above, .NET 6, and .NET 7. It is built on top of ASP.NET Core and has been tested and runs on all currently supported versions of ASP.NET Core up to 7.0. The client packages CoreWCF.RabbitMQ.Client and CoreWCF.Kafka.Client are supported on .NET 6 or later.

What's Changed

Security Fixes

GHSA-32jq-mv89-5rx7 - CoreWCF NetFraming based services can leave connections open when they should be closed.

Feedback

Your feedback is important and appreciated. Please use the discussion #1209 for your questions and comments.

Full Changelog: v1.4.1...v1.4.2