NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
NuGet
NuGet, #2385 most downloaded on NuGet
CoreWCF is a port of the service side of Windows Communication Foundation (WCF) to .NET Core. The goal of this project is to enable existing WCF services to move to .NET Core.
Latest stable
1.9.1
Last release 5 months ago
16 Jun 2026
Ships fairly regularly
a new release about every 4 months
Nearly every release is documented
notes for 28 of 28 stable releases
1 version withdrawn
withdrawn after publishing
127 years old
35 releases · first in 1900
Drag across the ruler to compare, or tap a release to open it.
This is a servicing release that addresses multiple security vulnerabilities. For full details, affected versions, and recommended mitigations, see ea…
CoreWCF.ConfigurationManager 1.9.1
CoreWCF.Http 1.9.1
CoreWCF.Kafka 1.9.1
CoreWCF.Kafka.Client 1.9.1
CoreWCF.MSMQ 1.9.1
CoreWCF.NetFramingBase 1.9.1
CoreWCF.NetNamedPipe 1.9.1
CoreWCF.NetTcp 1.9.1
CoreWCF.Primitives 1.9.1
CoreWCF.Queue 1.9.1
CoreWCF.RabbitMQ 1.9.1
CoreWCF.RabbitMQ.Client 1.9.1
CoreWCF.Templates 1.9.1
CoreWCF.UnixDomainSocket 1.9.1
CoreWCF.WebHttp 1.9.1
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.
This is a servicing release that addresses multiple security vulnerabilities. For full details, affected versions, and recommended mitigations, see each advisory linked below.
Your feedback is important and appreciated. Please use the discussion #1737 for your questions and comments.
Full Changelog: v1.9.0...v1.9.1
Your coding agent can read these notes before it upgrades. Set up the MCP server →
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 C
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
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.
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.
Your feedback is important and appreciated. Please use the discussion #1709 for your questions and comments.
Full Changelog: v1.8.0...v1.9.0
This is a servicing release that addresses multiple security vulnerabilities. For full details, affected versions, and recommended mitigations, see ea…
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
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.
This is a servicing release that addresses multiple security vulnerabilities. For full details, affected versions, and recommended mitigations, see each advisory linked below.
Your feedback is important and appreciated. Please use the discussion #1738 for your questions and comments.
Full Changelog: v1.8.0...v1.8.1
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 cleani…
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
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.
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.
[Obsolete] but is still functional by @g7ed6e in #1591Your feedback is important and appreciated. Please use the discussion #1628 for your questions and comments.
Full Changelog: v1.7.0...v1.8.0
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 C
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
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.
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.
Your feedback is important and appreciated. Please use the discussion #1543 for your questions and comments.
Full Changelog: v1.6.0...v1.7.0
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 should…
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
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.
The OperationContractAttribute properties IsInitiating and IsTerminating have been made available by @afifi-ins in #1332
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.
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.
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.
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.
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:
Your feedback is important and appreciated. Please use the discussion #1447 for your questions and comments.
Full Changelog: v1.5.2...v1.6.0
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.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
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.
GHSA-32jq-mv89-5rx7 - CoreWCF NetFraming based services can leave connections open when they should be closed.
Your feedback is important and appreciated. Please use the discussion #1288 for your questions and comments.
Full Changelog: v1.5.1...v1.5.2
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.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
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.
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.
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
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
Nothing published for this version
CoreWCF.ConfigurationManager 1.5.0-preview1 CoreWCF.Http 1.5.0-preview1 CoreWCF.Kafka 1.5.0-preview1 CoreWCF.Kafka.Client 1.5.0-preview1 CoreWCF.MSMQ
CoreWCF.ConfigurationManager 1.5.0-preview1
CoreWCF.Http 1.5.0-preview1
CoreWCF.Kafka 1.5.0-preview1
CoreWCF.Kafka.Client 1.5.0-preview1
CoreWCF.MSMQ 1.5.0-preview1
CoreWCF.NetFramingBase 1.5.0-preview1
CoreWCF.NetNamedPipe 1.5.0-preview1
CoreWCF.NetTcp 1.5.0-preview1
CoreWCF.Primitives 1.5.0-preview1
CoreWCF.Queue 1.5.0-preview1
CoreWCF.RabbitMQ 1.5.0-preview1
CoreWCF.RabbitMQ.Client 1.5.0-preview1
CoreWCF.Templates 1.5.0-preview1
CoreWCF.UnixDomainSocket 1.5.0-preview1
CoreWCF.WebHttp 1.5.0-preview1
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 CoreWCF.RabbitMQ.Client, CoreWCF.Kafka.Client, and CoreWCF.UnixDomainSocket packages only support .NET 6 or later.
We've added the CoreWCF.UnixDomainSocket package to provide support for using unix domain sockets with CoreWCF. This provides an alternative to NetNamedPipe and works on all supported platforms. This was contributed by @birojnayak from AWS.
Your feedback is important and appreciated. Please use the discussion https://github.com/CoreWCF/CoreWCF/discussions/1220 for your questions and comments.
Full Changelog: https://github.com/CoreWCF/CoreWCF/compare/v1.4.1...v1.5.0-preview1
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.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
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.
GHSA-32jq-mv89-5rx7 - CoreWCF NetFraming based services can leave connections open when they should be closed.
Your feedback is important and appreciated. Please use the discussion #1209 for your questions and comments.
Full Changelog: v1.4.1...v1.4.2
CoreWCF.Primitives 1.4.1 CoreWCF.Http 1.4.1 CoreWCF.WebHttp 1.4.1 CoreWCF.NetFramingBase 1.4.1 CoreWCF.NetTcp 1.4.1 CoreWCF.Queue 1.4.1 CoreWCF.Rabbit
CoreWCF.Primitives 1.4.1
CoreWCF.Http 1.4.1
CoreWCF.WebHttp 1.4.1
CoreWCF.NetFramingBase 1.4.1
CoreWCF.NetTcp 1.4.1
CoreWCF.Queue 1.4.1
CoreWCF.RabbitMQ 1.4.1
CoreWCF.RabbitMQ.Client 1.4.1
CoreWCF.Kafka 1.4.1
CoreWCF.Kafka.Client 1.4.1
CoreWCF.ConfigurationManager 1.4.1
CoreWCF.Templates 1.4.1
The MSMQ and NetNamedPipe packages are still in preview and will be in the next preview release.
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.
Your feedback is important and appreciated. Please use the discussion https://github.com/CoreWCF/CoreWCF/discussions/1209 for your questions and comments.
Full Changelog: https://github.com/CoreWCF/CoreWCF/compare/v1.4.0...v1.4.1
CoreWCF.Primitives 1.4.0 CoreWCF.Http 1.4.0 CoreWCF.WebHttp 1.4.0 CoreWCF.NetFramingBase 1.4.0 CoreWCF.NetTcp 1.4.0 CoreWCF.Queue 1.4.0 CoreWCF.Rabbit
CoreWCF.Primitives 1.4.0
CoreWCF.Http 1.4.0
CoreWCF.WebHttp 1.4.0
CoreWCF.NetFramingBase 1.4.0
CoreWCF.NetTcp 1.4.0
CoreWCF.Queue 1.4.0
CoreWCF.RabbitMQ 1.4.0
CoreWCF.RabbitMQ.Client 1.4.0
CoreWCF.Kafka 1.4.0
CoreWCF.Kafka.Client 1.4.0
CoreWCF.ConfigurationManager 1.4.0
CoreWCF.Templates 1.4.0
The MSMQ and NetNamedPipe packages are still in preview and will be in the next preview release.
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.
The CoreWCF.Queue package has come out of preview and provides a base set of classes for Queue based transports. New to this release are the packages CoreWCF.Kafka and CoreWCF.Kafka.Client, contributed by @g7ed6e. This enables using CoreWCF with the Apache Kafka distributed event streaming platform. The RabbitMQ packages CoreWCF.RabbitMQ and CoreWCF.RabbitMQ.Client are now out of preview. The MSMQ package is not out of preview yet.
Your feedback is important and appreciated. Please use the discussion https://github.com/CoreWCF/CoreWCF/discussions/1209 for your questions and comments.
Full Changelog: https://github.com/CoreWCF/CoreWCF/compare/v1.4.0-preview1...v1.4.0
CoreWCF.Primitives 1.4.0-preview1 CoreWCF.Http 1.4.0-preview1 CoreWCF.WebHttp 1.4.0-preview1 CoreWCF.NetFramingBase 1.4.0-preview1 CoreWCF.NetTcp 1.4.
CoreWCF.Primitives 1.4.0-preview1
CoreWCF.Http 1.4.0-preview1
CoreWCF.WebHttp 1.4.0-preview1
CoreWCF.NetFramingBase 1.4.0-preview1
CoreWCF.NetTcp 1.4.0-preview1
CoreWCF.NetNamedPipe 1.4.0-preview1
CoreWCF.Queue 1.4.0-preview1
CoreWCF.MSMQ 1.4.0-preview1
CoreWCF.RabbitMQ 1.4.0-preview1
CoreWCF.RabbitMQ.Client 1.4.0-preview1
CoreWCF.ConfigurationManager 1.4.0-preview1
CoreWCF.Templates 1.4.0-preview1
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 CoreWCF.RabbitMQ.Client package only supports .NET 6 or later.
We've added the CoreWCF.NetNamedPipe package to provide support for using named pipes. The code common to NetNamedPipe and NetTcp has been refactored into the CoreWCF.NetFramingBase. This makes it easier to add new transports based on top of streaming connections. Named Pipe support is only for Windows, but we'll be adding Unix Domain Socket support at a later date to provide an equivalent feature for using on Linux. This was contributed by @mconnew from Microsoft.
We've added the CoreWCF.Queue package which provides a base set of classes to make adding Queue based transports easier. We are releasing the new packages CoreWCF.MSMQ and CoreWCF.RabbitMQ (implements the AMQP protocol) to provide transports for using Windows MSMQ and RabbitMQ. We also currently have in development a queue based transport for Apache Kafka which will be released in the near future. The goal is to provide support for MSMQ as a step to migrating to other queue technologies. We're also releasing our first client package CoreWCF.RabbitMQ.Client which is only supported on .NET 6.0 or later. This is built on top of the WCF Client 6.0 pre-release package. This work was coordinated by @birojnayak from Amazon AWS, who wrote the design document for the generic Queue implementation. The majority of the code was contributed by @Ximik87 and @jonlouie. We also had code contributions from @birojnayak and @g7ed6e.
@bjornhellander exposed ServiceBehaviorAttribute.UseSynchronizationContext and added validating tests to confirm the property is working as expected. #983
When using HttpClientCredentialType.InheritedFromHost, we now issue an auth challenge if request is not authenticated if earlier middleware didn't do so, by @g7ed6e in #967
Fixed DI injection generated code when parameter name in implementation doesn't match parameter name in contract, by @g7ed6e in #1030
Fixed channel state transitions for HTTP which was breaking returning a fault when user extensibility throws an exception, by @mconnew in #1011
Fixed MTOM headers being incorrectly added to response body with HTTP, by @mconnew in #1049
Fixed compat behavior of [WebGet|WebInvoke]Attribute.Is[Request|Response]FormatSetExplicitly when using the attributes from System.ServiceModel.dll when using WebHttp on .NET Framework, by @arontsang in #1035
The version of dependent packages has changed in this release. We've had feedback that depending on the latest versions of packages causes problems for some users as it forces an upgrade. Starting from this release, we'll depend on the latest LTS versions of packages. This means we've downgraded requirements for a couple of dependencies from the 7.x version to the 6.x version. Upgrading and using the 7.x versions of packages in your own projects is still supported and intended to work.
As part of the work necessary to refactor common code between NetTcp and NetNamedPipe, CoreWCF now supports hosting NetTcp services when using an HTTP IServer other than Kestrel. This means you can use NetTcp with HttpSys or even hosted in IIS. Please note, NetTcp still doesn't support IIS hosted activation or port sharing, it still listens on its own socket and needs a unique port number.
None
Your feedback is important and appreciated. Please use the discussion https://github.com/CoreWCF/CoreWCF/discussions/1069 for your questions and comments.
Full Changelog: https://github.com/CoreWCF/CoreWCF/compare/v1.3.2...v1.4.0-preview1
CoreWCF.Primitives 1.3.2 CoreWCF.Http 1.3.2 CoreWCF.NetTcp 1.3.2 CoreWCF.WebHttp 1.3.2 CoreWCF.ConfigurationManager 1.3.2 CoreWCF.Templates 1.3.2
CoreWCF.Primitives 1.3.2
CoreWCF.Http 1.3.2
CoreWCF.NetTcp 1.3.2
CoreWCF.WebHttp 1.3.2
CoreWCF.ConfigurationManager 1.3.2
CoreWCF.Templates 1.3.2
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.
This release contains the follow bug fixes:
OpenApiResponse and FromServices together in the same contract by @g7ed6e in https://github.com/CoreWCF/CoreWCF/pull/970AuthorizationHandler<T> is added to DI with scoped lifetime by @g7ed6e in https://github.com/CoreWCF/CoreWCF/pull/948Your feedback is important and appreciated. Please use the existing v1.3.0 discussion https://github.com/CoreWCF/CoreWCF/discussions/946 for your questions and comments.
Full Changelog: https://github.com/CoreWCF/CoreWCF/compare/v1.3.1...v1.3.2
CoreWCF.Primitives 1.3.1 CoreWCF.Http 1.3.1 CoreWCF.NetTcp 1.3.1 CoreWCF.WebHttp 1.3.1 CoreWCF.ConfigurationManager 1.3.1 CoreWCF.Templates 1.3.1
CoreWCF.Primitives 1.3.1
CoreWCF.Http 1.3.1
CoreWCF.NetTcp 1.3.1
CoreWCF.WebHttp 1.3.1
CoreWCF.ConfigurationManager 1.3.1
CoreWCF.Templates 1.3.1
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. We have dropped support for .NET Core 3.1 as support has ended for that version. 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.
This release is to address a bug in the newly released ASP.NET Core authorization integration. When specifying InheritedByHost as the authentication mechanism, we are failing to reject unauthenticated requests. This bug only affects the new authentication and authorization feature introduced in v1.3.0.
Your feedback is important and appreciated. Please use the existing v1.3.0 discussion https://github.com/CoreWCF/CoreWCF/discussions/946 for your questions and comments.
Full Changelog: https://github.com/CoreWCF/CoreWCF/compare/v1.3.0...v1.3.1
The existing synchronous method have been deprecated using the Obsolete attribute and will cause a build warning. If you are overriding one of the exi…
CoreWCF.Primitives 1.3.0
CoreWCF.Http 1.3.0
CoreWCF.NetTcp 1.3.0
CoreWCF.WebHttp 1.3.0
CoreWCF.ConfigurationManager 1.3.0
CoreWCF.Templates 1.3.0
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. We have dropped support for .NET Core 3.1 as support has ended for that version. 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.
We now support attributing your service implementation with the ASP.NET Core [Authorize] attribute. We support specifying the Policy, but not Roles or AuthenticationSchemes. This support is currently only for HTTP although we're investigating ways to enable it for other transports. This work was done by @g7ed6e.
If you are using the CoreWCF.ConfigurationManager package for config file support, we now have support for configuring WebHttpBinding. Thanks to @jvnvenu for adding this support.
When using the CoreWCF template to create a new project, you will now have the option to add docker support. Thanks to @g7ed6e for adding this option.
ServiceAuthenticationManager and ServiceAuthorizationManager API modernizationThese two classes now have async versions of the virtual methods which you can override. The existing synchronous method have been deprecated using the Obsolete attribute and will cause a build warning. If you are overriding one of the existing synchronous virtual methods, your code will continue to function the same as it always has and will continue to do so for all future 1.x releases. The synchronous variations of the methods will likely be removed in a future 2.x release. You can safely suppress the build warning until you have migrated your implementation to the async methods. Thanks to @g7ed6e for making these async as this has long been a source of problems for developers using WCF on .NET Framework.
Your feedback is important and appreciated. Please use the discussion https://github.com/CoreWCF/CoreWCF/discussions/946 for your questions and comments.
Full Changelog: https://github.com/CoreWCF/CoreWCF/compare/v1.2.0...v1.3.0
CoreWCF.Primitives 1.2.1 CoreWCF.Http 1.2.1 CoreWCF.NetTcp 1.2.1 CoreWCF.WebHttp 1.2.1 CoreWCF.ConfigurationManager 1.2.1 CoreWCF.Templates 1.2.1
CoreWCF.Primitives 1.2.1
CoreWCF.Http 1.2.1
CoreWCF.NetTcp 1.2.1
CoreWCF.WebHttp 1.2.1
CoreWCF.ConfigurationManager 1.2.1
CoreWCF.Templates 1.2.1
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 Core 3.1, .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.
Full Changelog: https://github.com/CoreWCF/CoreWCF/compare/v1.2.0...v1.2.1
Your feedback is important and appreciated. Please use the discussion https://github.com/CoreWCF/CoreWCF/discussions/842 for your questions and comments.
CoreWCF.Primitives 1.2.0 CoreWCF.Http 1.2.0 CoreWCF.NetTcp 1.2.0 CoreWCF.WebHttp 1.2.0 CoreWCF.ConfigurationManager 1.2.0 CoreWCF.Templates 1.2.0
CoreWCF.Primitives 1.2.0
CoreWCF.Http 1.2.0
CoreWCF.NetTcp 1.2.0
CoreWCF.WebHttp 1.2.0
CoreWCF.ConfigurationManager 1.2.0
CoreWCF.Templates 1.2.0
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 Core 3.1, and .NET 6. 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 6.0.
When running on .NET Framework, if you have a contract using WebHttp attributes from the System.ServiceModel namespace such as WebInvokeAttribute, CoreWCF now recognizes them. You don't need to modify your code to use the CoreWCF equivalent attributes. When the WCF Core Client implements WebHttp at some future time, you will also be able to use the client packages to reference these attributes in a similar way. This was implemented by @arontsang in #752
If you have multiple services and modify the underlying ServiceHostBase using the ConfigureServiceHostBase<TService> extension method, it is now possible to provide a single delegate to configure each ServiceHostBase using the new extension method ConfigureAllServiceHostBase. The provided delegate will get called once for each service type. This was implemented by @g7ed6e in #815.
Previously you could add the service behavior UseRequestHeadersForMetadataAddressBehavior to tell CoreWCF to use the hostname and port from the incoming GET request for the WSDL to populate the server address in the returned WSDL document. This has some limitations as it doesn't modify the path or the scheme. Scenarios where this can be important are when using SSL offloading behind a reverse proxy/load balancer, or when using some url rewriting where the requested path is different than the locally hosted path. We have a new service behavior and interface which enables further customization of the URL. You can provide an implementation of CoreWCF.Description.IMetadataEndpointAddressProvider to the service behavior CoreWCF.Description.MetadataEndpointAddressServiceBehavior which will be called when a request for a WSDL is made. The method Uri GetEndpointAddress(HttpRequest httpRequest) is called, passing the HttpRequest for the WSDL request which can be examined as part of the calculation for the Uri which is returned. This enables scenarios such as returning a different address for internal clients and external clients or returning an HTTPS Uri when behind an SSL offloading load balancer. This was implemented by @g7ed6e in #822
TransferMode.Streamed by @mconnew in #806KeyValuePair<TKey, TValue> outside of a dictionary, and types returning their own schema definitions by @mconnew in #812 and #819MessageContract attributes being applied to a base class by @lukak-msft in #825Full Changelog: https://github.com/CoreWCF/CoreWCF/compare/v1.1.0...v1.2.0
Your feedback is important and appreciated. Please use the discussion https://github.com/CoreWCF/CoreWCF/discussions/842 for your questions and comments.
CoreWCF.Primitives 1.1.1 CoreWCF.Http 1.1.1 CoreWCF.NetTcp 1.1.1 CoreWCF.WebHttp 1.1.1 CoreWCF.ConfigurationManager 1.1.1 CoreWCF.Templates 1.1.1
CoreWCF.Primitives 1.1.1
CoreWCF.Http 1.1.1
CoreWCF.NetTcp 1.1.1
CoreWCF.WebHttp 1.1.1
CoreWCF.ConfigurationManager 1.1.1
CoreWCF.Templates 1.1.1
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 Core 3.1, .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.
Full Changelog: https://github.com/CoreWCF/CoreWCF/compare/v1.1.0...v1.1.1
Your feedback is important and appreciated. Please use the discussion https://github.com/CoreWCF/CoreWCF/discussions/735 for your questions and comments.
CoreWCF.Primitives 1.1.0 CoreWCF.Http 1.1.0 CoreWCF.NetTcp 1.1.0 CoreWCF.WebHttp 1.1.0 CoreWCF.ConfigurationManager 1.1.0 CoreWCF.Templates 1.1.0
CoreWCF.Primitives 1.1.0
CoreWCF.Http 1.1.0
CoreWCF.NetTcp 1.1.0
CoreWCF.WebHttp 1.1.0
CoreWCF.ConfigurationManager 1.1.0
CoreWCF.Templates 1.1.0
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 Core 3.1, and .NET 6. 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 6.0.
This was implemented by @g7ed6e in #590. You can install the templates by running dotnet new --install CoreWCF.Templates.
This was implemented by @jonlouie in #647. CoreWCF now requires the incoming HttpContext to have completed authentication using the scheme configured on the binding, and if it hasn't, send an authentication challenge to the client. The relevant authentication handler will need to be registered with ASP.NET Core in application code, but you will no longer need to enforce the authentication via middleware which executes before CoreWCF. When running on Windows and using Windows authentication, this will now enable impersonation. The ServiceSecurityContext will now be populated with the relevant infromation from the authentication.
This was implemented by @JonathanHopeDMRC in #665. There are three new properties on the OpenApiPropertyAttribute attribute. These are MinLength, MaxLength, and Format and directly map to the corresponding fields in the generated Swagger file. The class OpenApiOptions has the new property TagsSorter which enables providing an IComparer<OpenApiTag> to sort the tags as they will appear in the generated Swagger file.
This was done by @petarpetrovt in #718 and enables more easily examining the claim set for a client provided certificate via the ServiceSecurityContext.
Full Changelog: https://github.com/CoreWCF/CoreWCF/compare/v1.0.2..v1.1.0
Your feedback is important and appreciated. Please use the discussion https://github.com/CoreWCF/CoreWCF/discussions/735 for your questions and comments.
CoreWCF.Primitives 1.0.2 CoreWCF.Http 1.0.2 CoreWCF.NetTcp 1.0.2 CoreWCF.WebHttp 1.0.2 CoreWCF.ConfigurationManager 1.0.2
CoreWCF.Primitives 1.0.2
CoreWCF.Http 1.0.2
CoreWCF.NetTcp 1.0.2
CoreWCF.WebHttp 1.0.2
CoreWCF.ConfigurationManager 1.0.2
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 Core 3.1, and .NET 6. Support for .NET 5 ended as of May 10 2022. 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 6.0.
None
Full Changelog: https://github.com/CoreWCF/CoreWCF/compare/v1.0.1...v1.0.2
Your feedback is important and appreciated. Please use the discussion item for the v1.0 release at https://github.com/CoreWCF/CoreWCF/discussions/631 for your questions and comments.
CoreWCF.Primitives 1.0.1 CoreWCF.Http 1.0.1 CoreWCF.NetTcp 1.0.1 CoreWCF.WebHttp 1.0.1 CoreWCF.ConfigurationManager 1.0.1
CoreWCF.Primitives 1.0.1
CoreWCF.Http 1.0.1
CoreWCF.NetTcp 1.0.1
CoreWCF.WebHttp 1.0.1
CoreWCF.ConfigurationManager 1.0.1
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 Core 3.1, .NET 5, and .NET 6. 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 6.0.
None
Full Changelog: https://github.com/CoreWCF/CoreWCF/compare/v1.0.0...v1.0.1
Your feedback is important and appreciated. Please use the discussion item for the v1.0 release at https://github.com/CoreWCF/CoreWCF/discussions/631 for your questions and comments.
CoreWCF.Primitives 1.0.0 CoreWCF.Http 1.0.0 CoreWCF.NetTcp 1.0.0 CoreWCF.WebHttp 1.0.0 CoreWCF.ConfigurationManager 1.0.0
CoreWCF.Primitives 1.0.0
CoreWCF.Http 1.0.0
CoreWCF.NetTcp 1.0.0
CoreWCF.WebHttp 1.0.0
CoreWCF.ConfigurationManager 1.0.0
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 Core 3.1, .NET 5, and .NET 6. 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 6.0.
Full Changelog: https://github.com/CoreWCF/CoreWCF/compare/v1.0.0-preview2...v1.0.0
Your feedback is important and appreciated. We've created a discussion item at https://github.com/CoreWCF/CoreWCF/discussions/631 for your questions and comments.
CoreWCF.Primitives 1.0.0-preview2 CoreWCF.Http 1.0.0-preview2 CoreWCF.NetTcp 1.0.0-preview2 CoreWCF.WebHttp 1.0.0-preview2 CoreWCF.ConfigurationManage
CoreWCF.Primitives 1.0.0-preview2
CoreWCF.Http 1.0.0-preview2
CoreWCF.NetTcp 1.0.0-preview2
CoreWCF.WebHttp 1.0.0-preview2
CoreWCF.ConfigurationManager 1.0.0-preview2
This release depends on .NET Standard 2.0 and runs on any .NET version which supports .NET Standard 2.0. The GA release will occur after the support end date for .NET Framework 4.6.1 (April 26 2022) so this release will support .NET Framework 4.6.2 and above and .NET Core 3.1 and above. 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 6.0.
No new features in this release
Enum data types aren't correctly populated in the OpenAPI schema. The fix for this will be in the final release build.
Full Changelog: https://github.com/CoreWCF/CoreWCF/compare/v1.0.0-preview1...v1.0.0-preview2
Your feedback is important and appreciated. We've created a discussion item at https://github.com/CoreWCF/CoreWCF/discussions/613 for your questions and comments.
CoreWCF.Primitives 1.0.0-preview1 CoreWCF.Http 1.0.0-preview1 CoreWCF.NetTcp 1.0.0-preview1 CoreWCF.WebHttp 1.0.0-preview1 CoreWCF.ConfigurationManage
CoreWCF.Primitives 1.0.0-preview1
CoreWCF.Http 1.0.0-preview1
CoreWCF.NetTcp 1.0.0-preview1
CoreWCF.WebHttp 1.0.0-preview1
CoreWCF.ConfigurationManager 1.0.0-preview1
This release depends on .NET Standard 2.0 and runs on any .NET version which supports .NET Standard 2.0. The GA release will occur after the support end date for .NET Framework 4.6.1 (April 26 2022) so this release will support .NET Framework 4.6.2 and above and .NET Core 3.1 and above. 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 6.0.
WebSocketTransportSettings not being applied when using HTTPS (#568) - @mconnewWhen enabling WSDL support, if you have two types in your contract which are semantically the same, creation of the WSDL document will fail. For example, if you use List<string> in one DataContract, and IEnumerable<string> in another, they should be represented identically in the WSDL data schema. There is a bug in .NET where these are seen as different incompatible data types which are using the same schema definition and WSDL generation will fail. This will be fixed in the next preview release.
Full Changelog: https://github.com/CoreWCF/CoreWCF/compare/v0.4.0...v1.0.0-preview1
Your feedback is important and appreciated. We've created a discussion item at https://github.com/CoreWCF/CoreWCF/discussions/587 for your questions and comments.
CoreWCF.Primitives 0.4.0 CoreWCF.Http 0.4.0 CoreWCF.NetTcp 0.4.0 CoreWCF.ConfigurationManager 0.4.0
CoreWCF.Primitives 0.4.0
CoreWCF.Http 0.4.0
CoreWCF.NetTcp 0.4.0
CoreWCF.ConfigurationManager 0.4.0
Starting with 0.5.0, we have enabled tests to run for .NET 6. This means CoreWCF now supports .NET Core 3.1, .NET 5.0, .NET 6.0 and .NET Framework. We have dropped testing for .NET Core 2.1 as it is out of support. We still run tests against ASP.NET Core 2.1 as that is what runs on .NET Framework.
Your feedback is important and appreciated. We've created a discussion item at #520 for your questions and comments.
CoreWCF.Primitives 0.3.2 CoreWCF.Http 0.3.2 CoreWCF.NetTcp 0.3.2 CoreWCF.ConfigurationManager 0.3.2
CoreWCF.Primitives 0.3.2
CoreWCF.Http 0.3.2
CoreWCF.NetTcp 0.3.2
CoreWCF.ConfigurationManager 0.3.2
Bump System.DirectoryServices.Protocols from 5.0.0 to 5.0.1. This is due to a critical security bug in System.DirectoryServices.Protocols which is used by CoreWCF for populating claims information when using Windows authentication with security mode TransportWithMessageCredentials. This update is critical if you use this scenario on Linux or MacOS. Windows services are unaffected. More information can be found in the .NET Core security advisory here.
None
CoreWCF.Primitives 0.3.1 CoreWCF.Http 0.3.1 CoreWCF.NetTcp 0.3.1 CoreWCF.ConfigurationManager 0.3.1
CoreWCF.Primitives 0.3.1
CoreWCF.Http 0.3.1
CoreWCF.NetTcp 0.3.1
CoreWCF.ConfigurationManager 0.3.1
This release depends on .NET Standard 2.0 and runs on any .NET version which supports .NET Standard 2.0. This means.NET Framework 4.6.1 and above and .NET Core 3.1 and above. 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 5.0.
The new CoreWCF.ConfigurationManager package would fail to load the config if an endpoint had no name. A similar issue was happening with the service definition. This release fixes that issue. It also changes 2 of the new public apis. While fixing the issue, we discovered that 2 members on the new interface CoreWCF.Configuration.IConfigurationHolder would allow a cleaner implementation if they were modified slightly. The property ConcurrentDictionary<string, ServiceEndpoint> Endpoints { get; } has been changed to ISet<ServiceEndpoint> Endpoints { get; } and the method IXmlConfigEndpoint GetXmlConfigEndpoint(string name); has been changed to IXmlConfigEndpoint GetXmlConfigEndpoint(ServiceEndpoint endPoint);. This was to avoid the introduction of an artificial key which could potentially have problems with name collisions. This interface isn't referenced when configuring a CoreWCF service to use a .config file so we don't expect this change to affect anybody who has already begun using this new package.
The documentation is still being worked on. Most classes which exist in .NET Framework under the System.ServiceModel namespace should have the same behavior in CoreWCF. Until we have documentation published, please refer to the .NET Framework WCF documentation.
You can find samples for some common scenarios in the Samples folder of the repo.
Your feedback is important and appreciated. We've created a discussion item at #453 for your questions and comments.
CoreWCF.Primitives 0.3.0 CoreWCF.Http 0.3.0 CoreWCF.NetTcp 0.3.0 CoreWCF.ConfigurationManager 0.3.0
CoreWCF.Primitives 0.3.0
CoreWCF.Http 0.3.0
CoreWCF.NetTcp 0.3.0
CoreWCF.ConfigurationManager 0.3.0
This release depends on .NET Standard 2.0 and runs on any .NET version which supports .NET Standard 2.0. This means.NET Framework 4.6.1 and above and .NET Core 2.1 and above. It is built on top of ASP.NET Core 2.1, and has been tested and runs on all currently supported versions of ASP.NET Core up to 5.0.
We have a new package, CoreWCF.ConfigurationManager. This is used to provide partial support for using your app.config configuration from .NET Framework. Here is a summary of all the new features in 0.3.0.
The documentation is still being worked on. Most classes which exist in .NET Framework under the System.ServiceModel namespace should have the same behavior in CoreWCF. Until we have documentation published, please refer to the .NET Framework WCF documentation.
You can find samples for some common scenarios in the Samples folder of the repo.
Your feedback is important and appreciated. We've created a discussion item at #443 for your questions and comments.
CoreWCF.Primitives 0.2.1 CoreWCF.Http 0.2.1 CoreWCF.NetTcp 0.2.1
CoreWCF.Primitives 0.2.1
CoreWCF.Http 0.2.1
CoreWCF.NetTcp 0.2.1
This release depends on .NET Standard 2.0 and runs on any .NET version which supports .NET Standard 2.0. This means.NET Framework 4.6.1 and above and .NET Core 2.1 and above. It is built on top of ASP.NET Core 2.1, and has been tested and runs on all currently supported versions of ASP.NET Core up to 5.0.
None
If you are using an HTTPS endpoint, you must pass BasicHttpSecurityMode.Transport to the constructor of BasicHttpBinding.
The documentation is still being worked on. Most classes which exist in .NET Framework under the System.ServiceModel namespace should have the same behavior in CoreWCF. Until we have documentation published, please refer to the .NET Framework WCF documentation.
You can find samples for some common scenarios in the Samples folder of the repo.
Your feedback is important and appreciated. We've created a discussion item at #408 for your questions and comments.
CoreWCF.Primitives 0.2.0 CoreWCF.Http 0.2.0 CoreWCF.NetTcp 0.2.0
CoreWCF.Primitives 0.2.0
CoreWCF.Http 0.2.0
CoreWCF.NetTcp 0.2.0
This release depends on .NET Standard 2.0 and runs on any .NET version which supports .NET Standard 2.0. This means.NET Framework 4.6.1 and above and .NET Core 2.1 and above. It is built on top of ASP.NET Core 2.1, and has been tested and runs on all currently supported versions of ASP.NET Core up to 5.0.
The following features are new to CoreWCF 0.2.0
The documentation is still being worked on. Most classes which exist in .NET Framework under the System.ServiceModel namespace should have the same behavior in CoreWCF. Until we have documentation published, please refer to the .NET Framework WCF documentation.
You can find samples for some common scenarios in the Samples folder of the repo. For this release we have some new sample scenarios and the samples have been cleaned up a bit thanks to @JohnLeyva.
Major Contributors in order of contribution (500+ lines of code added):
@birojnayak (Amazon AWS)
@JohnLeyva
@mconnew (Microsoft)
Other code contributors:
@g7ed6e, @ovebastiansen, @Grauenwolf, @josellm, @BradBarnich
Your feedback is important and appreciated. We've created a discussion item at #390 for your questions and comments.
CoreWCF.Primitives 0.1.0 CoreWCF.Http 0.1.0 CoreWCF.NetTcp 0.1.0
CoreWCF.Primitives 0.1.0
CoreWCF.Http 0.1.0
CoreWCF.NetTcp 0.1.0
This release depends on .NET Standard 2.0 and runs on any .NET version which supports .NET Standard 2.0. This means.NET Framework 4.6.1 and above and .NET Core 2.1 and above. It is built on top of ASP.NET Core 2.1.
The following features are supported in CoreWCF
The documentation is still being worked on. Most classes which exist in .NET Framework under the System.ServiceModel namespace should have the same behavior in CoreWCF. Until we have documentation published, please refer to the .NET Framework WCF documentation.
You can find samples for some common scenarios in the Samples folder of the repo.
Major Contributors (10,000+ lines of code):
@mconnew (Microsoft)
@birojnayak (Amazon AWS)
Other code contributors:
@imcarolwang, @danielcrenna, @v-fangfc, @nschonni, @willaimyou, @Treit, @DamirAinullin, @VorTechS, @0x53A, @ZhaodongTian, @voronov-maxim, @edberg, @FreeAndNil, @Daniel-Svensson, @v-yarli
Your feedback is important and appreciated. We've created a discussion item at #309 for your questions and comments.
Nothing published for this version
Nothing published for this version
One column per quarter.