This month, there have been several significant releases in the CoreWCF ecosystem. Version 1.4.0 was released, featuring new transport options such as RabbitMQ (AMQP) and Apache Kafka. While these additions were well-received, it's worth mentioning that the transports MSMQ (Microsoft Message Queuing) and NetNamedPipe remain in the preview stage, indicating ongoing development efforts for these additions in the future.
To address package dependency version, a quick follow-up was made with the release of v1.4.1. As reported, this patch release did not introduce any code changes, focusing solely on updating dependencies. The detailed release notes about these dependency changes are available for readers on the official GitHub repository page.
In the latest CoreWCF release, it remains compatible with .NET Standard 2.0, supporting .NET Framework versions 4.6.2 and higher, alongside .NET 6 and 7. This compatibility extends to ASP.NET Core, tested across versions up to 7.0 as reported. Also, regarding the new features, they include CoreWCF.Queue package which comes out of preview and delivers a base set of classes for Queue-based transports. Furthermore, contributions from the community bring integration of CoreWCF with the Apache Kafka distributed event streaming platform
Likewise, this release also introduces new features and APIs, such as making WindowsClaimSet and ServiceCredentialsSecurityTokenManager public. Additionally, CoreWCF now provides an API to enable AuthorizationPolicy support with explicit HTTP client credential types, enhancing customization and security. This release also addresses several bug fixes, enhancing stability and security; a complete list of bug fixes is available on the release post of the 1.4.0 version.
Additionally, CoreWCF revealed v1.5.0-preview1, which brings a couple of bug fixes for NetNamedPipe support and introduces support for Unix domain sockets through the CoreWCF.UnixDomainSocket package. It's important to note that this version remains in preview status, as official client packages from the dotnet/wcf project have not yet been released. However, as reported there are unofficial client packages which can be accessed from a temporary Nuget feed, with full details about this can be found in the official blog post.
In addition to the first release announcement, last week the X (formerly Twitter) post from Matt Connew. The post revealed some exciting news the CoreWCF project has reached a significant milestone of 1 million package downloads.
Matt Connew wrote the following:
CoreWCF just hit a big milestone, 1 million package downloads!! Thanks to everyone in the community who has contributed over the years and helped make the project what it is.
Lastly, the CoreWCF project opens an invitation to the companies which are using its services in production. Matt Connew wrote the following on the GitHub release post:
We would like to invite any companies who are using CoreWCF in production to have their name listed as a user of CoreWCF in the main README.MD of the CoreWCF repo. We would like to include a link to your company website along with your company name or logo. Please send an email to contact@corewcf.net from an email address from the same domain as the url you wish to have linked with details of how you would like the link to appear.
