Our great sponsors
-
Server-Client-Communication-WCF
CoreWCF on DotNet 5.0 called from a WCF .net framework 4.7.2 with nettcp streaming
-
referencesource
Source from the Microsoft .NET Reference Source that represent a subset of the .NET Framework
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
Sending hugs! Last I looked (2 years ago??!??), support was already pretty good. https://github.com/ewinnington/Server-Client-Communication-WCF
Not enough people care. And you can compile the APIs yourself from the .NET Framework reference source if you really want it. System.Messaging was added to the .NET Framework reference source in this PR.
There's ongoing work on adding generic queue support. The first two concrete implementations should be MSMQ and RabbitMq from what I recall, though MSMQ will be windows only. But the nice thing about the work is it also opens up other types of message queues for WCF (e.g. Azure Service Bus, RabbitMq, Amazon SQS etc...).
Sorry about that but I think System.Optimization is dead as a dodo. Would Google.ORTools help (https://developers.google.com/optimization)
If you want something a bit close to .net framework's bundling feature, there's this library that I've used on one of our projects. The syntax is a bit different, but overall it should be less work needed than moving the whole bundling system to use the nodejs ecosystem.