CoreWCF - CoreWCF v1.5.2 Latest Release

Published by mconnew 7 months ago

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

https://github.com/CoreWCF/CoreWCF/security/advisories/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 https://github.com/CoreWCF/CoreWCF/discussions/1288 for your questions and comments.

Full Changelog: https://github.com/CoreWCF/CoreWCF/compare/v1.5.1...v1.5.2

CoreWCF - CoreWCF v1.4.2

Published by mconnew 7 months ago

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

https://github.com/CoreWCF/CoreWCF/security/advisories/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 https://github.com/CoreWCF/CoreWCF/discussions/1209 for your questions and comments.

Full Changelog: https://github.com/CoreWCF/CoreWCF/compare/v1.4.1...v1.4.2

CoreWCF - CoreWCF v1.5.1

Published by mconnew 11 months ago

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 https://github.com/CoreWCF/CoreWCF/discussions/1288 for your questions and comments.

Full Changelog: https://github.com/CoreWCF/CoreWCF/compare/v1.5.0-preview1...v1.5.1

CoreWCF - CoreWCF v1.5.0-preview1

Published by mconnew about 1 year ago

Release Notes

Package Info

.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 CoreWCF.RabbitMQ.Client, CoreWCF.Kafka.Client, and CoreWCF.UnixDomainSocket packages only support .NET 6 or later.

New Features

Unix Domain Socket support

We've added the CoreWCF.UnixDomainSocketpackage 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.

What's Changed

Bug Fixes

Cleanup the shared memory object for named pipe which was preventing restarting a service in the same process by @mconnew in #1195
Fix hash algorithm used to shorten long paths for net.pipe urls by @mconnew in #1196

Feedback

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 - CoreWCF v1.4.1

Published by mconnew about 1 year ago

Release Notes

Package Info

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.

.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

Bug Fixes

Some packages dependency version updates were missed when updating to latest versions by @mconnew in #1215 and #1219

Feedback

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 - CoreWCF v1.4.0

Published by mconnew about 1 year ago

Release Notes

Package Info

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.

.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.

New Features

Queue Transport support

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.

What's Changed

Bug Fixes

Enable sending unsecured faults when using TransportWithMessageCredentials by @mconnew in #1083
Reading incoming streamed message failed if chunk size and data arrive in different receive calls by @chrjstophoros in #1100
Fixed missing argument in TimeoutException message causing different exception by @FirstClassCitizenFCC in ##1111
Fix ServiceAuthorizationBehavior lifetime to enable override per registered Service by @g7ed6e in #1119
Fixed Xml signature validation of requests from non-WCF clients by @gekiss in #1180
Fixed calling OperationContext.Current before the host started broke OperationContext.Current in operations by @DxCK in #1157
Added Kafka packages by @g7ed6e in #943
Fixed WSDL generation when AddressingVersion.WSAddressingAugust2004 was used by @ioda in #1112
Improved interop with Apache CFX which can't handle the "role" attribute being applied to the Security header by @mconnew in #1197
Fixed hosted services not being correctly stopped when disposing but not stopping WebApplication by @g7ed6e and @mconnew in #1205 and #1206

New Features/APIs

WindowsClaimSet made public by @afifi-ins in #1090
ServiceCredentialsSecurityTokenManager made public by @afifi-ins in #1088
Add explicit cast to Saml2SecurityToken to enable retrieving underlying Microsoft.IdentityModel.Tokens.Saml2.Saml2SecurityToken instance by @birojnayak in #1074
Added API to enable using AuthorizationPolicy support with explicit HTTP client credential type by @g7ed6e in #1148

Other changes

Non-shipping contributions

Make it easy to locally host SourceBrowser for CoreWCF by @mconnew in #1156

New Contributors

@chrjstophoros made their first contribution in #1100
@FirstClassCitizenFCC made their first contribution in #1111
@gekiss made their first contribution in #1180
@DxCK made their first contribution in #1157
@ioda made their first contribution in #1112

Feedback

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 - CoreWCF v1.4.0-preview1

Published by mconnew over 1 year ago

Release Notes

Package Info

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

.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 CoreWCF.RabbitMQ.Client package only supports .NET 6 or later.

New Features

Named Pipe support

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.

Queue Transport support

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.

Add support for ServiceBehaviorAttribute.UseSynchronizationContext

@bjornhellander exposed ServiceBehaviorAttribute.UseSynchronizationContext and added validating tests to confirm the property is working as expected. #983

What's Changed

Bug Fixes

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

Other changes

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.

Non-shipping contributions

None

New Contributors

@bjornhellander made their first contribution in https://github.com/CoreWCF/CoreWCF/pull/983

Feedback

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 - CoreWCF v1.3.2

Published by mconnew over 1 year ago

Release Notes

Package Info

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

.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.

What's Changed

This release contains the follow bug fixes:

WebHttpBinding now supports ASP.NET Core authentication and policy based authorization using InheritedByHost by @g7ed6e in https://github.com/CoreWCF/CoreWCF/pull/951
Fixed Windows auth with TransportWithMessageCredentials on .NET 7.0 by @nmangue in https://github.com/CoreWCF/CoreWCF/pull/917
Fixed issue with source generator crashing when using OpenApiResponse and FromServices together in the same contract by @g7ed6e in https://github.com/CoreWCF/CoreWCF/pull/970
Fixed issue with MTOM support not handling responses larger than 2GB. Also improves memory usage for some scenarios using MTOM by @afifi-ins in https://github.com/CoreWCF/CoreWCF/pull/1005
Fixed ASP.NET Core authentication authzn integration when the provided AuthorizationHandler<T> is added to DI with scoped lifetime by @g7ed6e in https://github.com/CoreWCF/CoreWCF/pull/948

Feedback

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.1...v1.3.2

CoreWCF - CoreWCF v1.3.1

Published by mconnew almost 2 years ago

Release Notes

Package Info

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

.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. 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.

What's Changed

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.

Fixed authentication when using InheritedByHost by @g7ed6e in https://github.com/CoreWCF/CoreWCF/pull/961

Feedback

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

CoreWCF - CoreWCF v1.3.0

Published by mconnew almost 2 years ago

Release Notes

Package Info

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

.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. 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.

New Features

ASP.NET Core Authorization support

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.

Configuration support for WebHttpBinding

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.

New options on CoreWCF Template

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 modernization

These 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.

What's Changed

Drop UriEx by @g7ed6e in https://github.com/CoreWCF/CoreWCF/pull/855
Fix NetTcp to correctly apply MaxReceivedMessageSize by @mconnew in https://github.com/CoreWCF/CoreWCF/pull/856
Make ServiceAuthorizationManager async by @g7ed6e in https://github.com/CoreWCF/CoreWCF/pull/852
Fix WSDL issues due to runtime changes in net7.0 support by @g7ed6e in https://github.com/CoreWCF/CoreWCF/pull/837
Async global exception logging missing user-code stacktrace by @OlofBlomqvist in https://github.com/CoreWCF/CoreWCF/pull/863
Make ServiceAuthenticationManager async by @g7ed6e in https://github.com/CoreWCF/CoreWCF/pull/851
Added Check That Config File Exists by @lukedukeus in https://github.com/CoreWCF/CoreWCF/pull/879
Update CoreWCF.Templates target runtimes by @g7ed6e in https://github.com/CoreWCF/CoreWCF/pull/882
OpenApiSchemaBuilder compatibility with System.ServiceModel.Web Attributes by @arontsang in https://github.com/CoreWCF/CoreWCF/pull/897
RequestDelegateHandler.AcceptWebSocketAsync does not support SubProtocol == null by @arontsang in https://github.com/CoreWCF/CoreWCF/pull/909
Fix binding to empty address by @arontsang in https://github.com/CoreWCF/CoreWCF/pull/908
Make templates findable in VS when searching for 'Web' by @g7ed6e in https://github.com/CoreWCF/CoreWCF/pull/895
Introduce ASP.NET Core Authorization support by @g7ed6e in https://github.com/CoreWCF/CoreWCF/pull/850
Enable VS 2022 builtin docker support and wording for https in templates by @g7ed6e in https://github.com/CoreWCF/CoreWCF/pull/937
Fix logger category in ServiceModelApplicationBuilderExtensions by @mus65 in https://github.com/CoreWCF/CoreWCF/pull/929
WebHttpBinding config section support added by @jvnvenu in https://github.com/CoreWCF/CoreWCF/pull/927
Update package versions by @mconnew in https://github.com/CoreWCF/CoreWCF/pull/942
drop netcoreapp3.1 from CoreWCF.Templates by @g7ed6e in https://github.com/CoreWCF/CoreWCF/pull/945

Non-shipping contributions

Update debug tests to use 15m timeout too by @mconnew in https://github.com/CoreWCF/CoreWCF/pull/880
Remove net5.0 unit tests by @g7ed6e in https://github.com/CoreWCF/CoreWCF/pull/885
Add hint to find test causing CI error 'There is no currently active test.' by @g7ed6e in https://github.com/CoreWCF/CoreWCF/pull/928
Fix OneWayPatternTest by @g7ed6e in https://github.com/CoreWCF/CoreWCF/pull/938
Design document for generic queue transport in CoreWCF by @birojnayak in https://github.com/CoreWCF/CoreWCF/pull/736

New Contributors

@OlofBlomqvist made their first contribution in https://github.com/CoreWCF/CoreWCF/pull/863
@lukedukeus made their first contribution in https://github.com/CoreWCF/CoreWCF/pull/879
@mus65 made their first contribution in https://github.com/CoreWCF/CoreWCF/pull/929
@jvnvenu made their first contribution in https://github.com/CoreWCF/CoreWCF/pull/927

Feedback

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 - CoreWCF v1.1.1

Published by mconnew almost 2 years ago

Release Notes

Package Info

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

.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 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.

What's Changed

Backport net7 support to 1.1. Work originally done by @g7ed6e in https://github.com/CoreWCF/CoreWCF/pull/837

Full Changelog: https://github.com/CoreWCF/CoreWCF/compare/v1.1.0...v1.1.1

Feedback

Your feedback is important and appreciated. Please use the discussion https://github.com/CoreWCF/CoreWCF/discussions/735 for your questions and comments.

CoreWCF - CoreWCF v1.2.1

Published by mconnew almost 2 years ago

Release Notes

Package Info

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

.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 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.

What's Changed

Backport net7 support to 1.2. Work originally done by @g7ed6e in https://github.com/CoreWCF/CoreWCF/pull/837
Fixed NetTcp streaming to respect specified MaxReceivedMessageSize specified on binding by @mconnew in https://github.com/CoreWCF/CoreWCF/pull/856

Full Changelog: https://github.com/CoreWCF/CoreWCF/compare/v1.2.0...v1.2.1

Feedback

Your feedback is important and appreciated. Please use the discussion https://github.com/CoreWCF/CoreWCF/discussions/842 for your questions and comments.

CoreWCF - CoreWCF v1.2.0

Published by mconnew about 2 years ago

Release Notes

Package Info

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

.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 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.

New Features

Compatibility with System.ServiceModel.Web attributes

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

Ability to configure all ServiceHostBase instances with a single delegate

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.

More flexibility in modifying the WSDL URL

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

What's Changed

Fixed possible null reference exception during OpenAPI doc gen. by @JonathanHopeDMRC in #729
Fix bug when using multiple services with NetTcp and TransferMode.Streamed by @mconnew in #806
Changed System.Security.Cryptography.Xml dependency from 5.0.0 to 6.0.1 by @dependabot in #798
Ported IOThreadScheduler performance improvements from WCF Core Client by @jonlouie in #794
Improved confusing exception message when using a service type not in DI and without a default constructor by @tom-englert in #733
ServerFramingDuplexSessionChannel.DecodeMessage made async by @g7ed6e in #810
Fixed MaxBufferPoolSize not propagating for HTTP based bindings which was causing worse performance with large messages by @jonlouie in #775
Fixed multiple WSDL issues, including usage of KeyValuePair<TKey, TValue> outside of a dictionary, and types returning their own schema definitions by @mconnew in #812 and #819
Fixed problem with MessageContract attributes being applied to a base class by @lukak-msft in #825
Fixed service method parameter injection code generator performance issues by @g7ed6e in #820
Updated dependent packages to latest versions (except System.DirectoryServices.Protocols which has a problem on .NET Framework in it's latest release) by @mconnew in #838

Non-shipping contributions

Updated Walkthrough.md to fix sample link by @pea-sys in #740
Fix CoreWCF project template image path in Walkthrough.md by @g7ed6e in #772

New Contributors

@pea-sys made their first contribution in #740
@arontsang made their first contribution in #752
@tom-englert made their first contribution in #733
@lukak-msft made their first contribution in #825

Full Changelog: https://github.com/CoreWCF/CoreWCF/compare/v1.1.0...v1.2.0

Feedback

Your feedback is important and appreciated. Please use the discussion https://github.com/CoreWCF/CoreWCF/discussions/842 for your questions and comments.

CoreWCF - CoreWCF v1.1.0

Published by mconnew over 2 years ago

Release Notes

Package Info

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

.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 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.

New Features

CoreWCF templates for use with dotnet new

This was implemented by @g7ed6e in #590. You can install the templates by running dotnet new --install CoreWCF.Templates.

Impersonation support with Transport Security over HTTP

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.

New APIs to modify generated Swagger file with WebHttpBinding

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.

The class X509CertificateClaimSet has been made public

This was done by @petarpetrovt in #718 and enables more easily examining the claim set for a client provided certificate via the ServiceSecurityContext.

What's Changed

Fixed sending fault message on security exception by @jonlouie in #684
Fix MessageBuffer.CreateMessage when Security is not null by @mconnew in #690
Fixed WebHttpBinding issue with streamed mode transfer and Stream response which aborted response on last buffer by @JonathanHopeDMRC in #694
Fixed multiple sync over async call paths when closing a WebSockets channel by @gvkries in #711
Fixed double closing a WebSocket which caused an exception to be thrown by @gvkries in #709

New Contributors

@gvkries made their first contribution in https://github.com/CoreWCF/CoreWCF/pull/709

Full Changelog: https://github.com/CoreWCF/CoreWCF/compare/v1.0.2..v1.1.0

Feedback

Your feedback is important and appreciated. Please use the discussion https://github.com/CoreWCF/CoreWCF/discussions/735 for your questions and comments.

CoreWCF - CoreWCF v1.0.2

Published by mconnew over 2 years ago

Release Notes

Package Info

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

.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 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.

New Features

None

What's Changed

Fixed WSDL generation when multiple services are in the application by @mconnew in #660
Fixed potential race condition at service startup which could prevent CoreWCF service from finishing initialization by @mconnew in #667
Worked around bug in Application Insights Azure extensions which was preventing CoreWCF service from starting by @mconnew in #667

Full Changelog: https://github.com/CoreWCF/CoreWCF/compare/v1.0.1...v1.0.2

Feedback

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 - CoreWCF v1.0.1

Published by mconnew over 2 years ago

Release Notes

Package Info

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

.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 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.

New Features

None

What's Changed

Prevent CoreWCF source generator from interfering with ASP.NET Core MVC Controller when using FromService attribute by @g7ed6e in #636
Reduced the number of scenarios where AllowSynchronousIO is needed by @mconnew in #648

Full Changelog: https://github.com/CoreWCF/CoreWCF/compare/v1.0.0...v1.0.1

Feedback

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 - CoreWCF v1.0.0

Published by mconnew over 2 years ago

Release Notes

Package Info

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

.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 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.

New Features

Custom Binding support for Configuration (@kbrowdev)

What's Changed

Fixed some OpenAPI documentation generation issues by @JonathanHopeDMRC in https://github.com/CoreWCF/CoreWCF/pull/617
Fixed Url base address for NetTcp when listening on IPv6 by @FreeAndNil in https://github.com/CoreWCF/CoreWCF/pull/609
Fixed Get only collection support in WSDL generation by @roend83 in https://github.com/CoreWCF/CoreWCF/pull/616
Added support for MessagePropertyAttribute and fixed support for MessageHeaderArrayAttribute by @mconnew in https://github.com/CoreWCF/CoreWCF/pull/623
Enable compression over NetTcp by @jonlouie in https://github.com/CoreWCF/CoreWCF/pull/627
Fixing bad requests to return a 400 response to match WCF by @mconnew in https://github.com/CoreWCF/CoreWCF/pull/626
Fixed deriving SecurityTokenManager as abstract method was internal by @gougeman in https://github.com/CoreWCF/CoreWCF/pull/630
Added configuration support for custom bindings by @kbrowdev in https://github.com/CoreWCF/CoreWCF/pull/578

New Contributors

@jonlouie made their first contribution in https://github.com/CoreWCF/CoreWCF/pull/627
@gougeman made their first contribution in https://github.com/CoreWCF/CoreWCF/pull/630
@kbrowdev made their first contribution in https://github.com/CoreWCF/CoreWCF/pull/578

Full Changelog: https://github.com/CoreWCF/CoreWCF/compare/v1.0.0-preview2...v1.0.0

Feedback

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 - v1.0.0-preview2

Published by mconnew over 2 years ago

Release Notes

Package Info

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

.NET Compatibility

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.

New Features

No new features in this release

Bug Fixes

Increased dependency version of Microsoft.IdentityModel.* packages to 6.17.0 (#598) - @birojnayak
Fixed bug where a NullReferenceException could get thrown when using WebHttp if AddServiceModelWebServices hasn't been called (#601) - @tallalnparis4ev
Fixed bug where wsdl and xsd URL query parameter values weren't parsed correctly (#607) - @roend83
Created workaround for .NET runtime bugs when creating XSD schema for semantically equivalent data types (#605) - @mconnew
Removed unnecessary and broken static method SecurityTokenHandlerCollection.CreateDefaultSecurityTokenHandlerCollection() (#611) - @birojnayak

Known Issues

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

New Contributors

@tallalnparis4ev made their first contribution in https://github.com/CoreWCF/CoreWCF/pull/601
@roend83 made their first contribution in https://github.com/CoreWCF/CoreWCF/pull/607

Feedback

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 - CoreWCF 1.0.0-preview1

Published by mconnew over 2 years ago

Release Notes

Package Info

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

.NET Compatibility

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.

New Features

WS-Federation support - Biroj Nayak, Amazon AWS (@birojnayak)
WebHttpBinding support with OpenApi feature - Jonathan Hope, Digimarc (@JonathanHopeDMRC)
WSDL support, including ServiceDebugBehavior - Matt Connew, Microsoft (@mconnew )
New support for injecting HttpContext, HttpRequest, and HttpResponse objects into service implementation methods. This also includes supporting the ASP.NET Core FromServicesAttribute in addition to the CoreWCF InjectedAttribute - Guillaume Delahaye (@g7ed6e)

Bug Fixes

When an invalid binding configuration is used, a NullReferenceException was thrown when the dispatcher couldn't be created (#576) - @g7ed6e
IIS site bindings using wildcard hostnames (e.g. *.example.com) would cause CoreWCF to fail to start the service (#570) - @absinghal
Fix WebSocketTransportSettings not being applied when using HTTPS (#568) - @mconnew
When a NetTcp client attempted to connect to an incorrect endpoint, the connection would be aborted instead of returning the correct EndpointNotFound status to the client (#531) - @cyanite
Fixed problem where multiple endpoints with different contracts at the same address would fail (@527) - @cyanite
Improved exception message when adding endpoint to service builder for a service type that hasn't yet been added (#524) - @g7ed6e
GetKnownTypes for dynamic known type list (#516) - @absinghal
Make the DispatchOperation.CallContextInitializers property public (#499) - @JeffLeBert

Known Issues

When 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

New Contributors

@progalgo made their first contribution in https://github.com/CoreWCF/CoreWCF/pull/517
@absinghal made their first contribution in https://github.com/CoreWCF/CoreWCF/pull/516
@cyanite made their first contribution in https://github.com/CoreWCF/CoreWCF/pull/531

Feedback

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 - CoreWCF 0.4.0

Published by mconnew almost 3 years ago

Release Notes

Package Info

CoreWCF.Primitives 0.4.0
CoreWCF.Http 0.4.0
CoreWCF.NetTcp 0.4.0
CoreWCF.ConfigurationManager 0.4.0

.NET Compatibility

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.

New Features

Added asynchronous support to SecurityTokenAuthenticator. - @g7ed6e
Ported MTOM implementation from WCF Core client to provide MTOM message encoding support. - @g7ed6e
Added support for scoped IServiceProvider available from OperationContext.Current.InstanceContext.Extensions.Find() - @g7ed6e
Enabled ServiceSecurityContext.GetIdentities api including providing tests. - @JeffLeBert
Added MessageVersion values which were missing from .NET Framework. - @mconnew
Added support to enable allowing DI to provide concrete type by only specifying an interface when configuring CoreWCF. - @Danielku15
New source generator to enable easily adding DI injected parameters to service operations. - @g7ed6e

Bug Fixes

Fixed HttpRequest.PathBase being broken when middleware runs after the UseServiceModel middleware. - @mconnew
Fixed unhandled exception in RequestReplyCorrelator during a race condition - @mconnew
Fixed a Task which wasn't awaited in service dispatcher which could cause a service channel to be used before it was opened. Ported AsyncLocal for WCF Core client to fix broken implementation in CoreWCF. - @Danielku15
Fixed FaultException namespace not being correctly handled when using System.ServiceModel.FaultContext - @g7ed6e