CoreWCF
runtimelab
Our great sponsors
CoreWCF | runtimelab | |
---|---|---|
24 | 52 | |
1,596 | 1,329 | |
1.1% | 1.1% | |
7.8 | 5.1 | |
5 days ago | 6 days ago | |
C# | ||
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
CoreWCF
-
How do I approach migrating from .net framework WCF to .net core web api
CoreWCF might be of some use.
-
Having a heck of a time getting WCF web.config working correctly.
You can open a discussion in the CoreWCF repo:
-
Why WCF? Am I wrong for hating it so much?
In the later versions you could avoid almost all the XML mess by configuring all of the settings in code. The experience is pretty close to gRPC imo, one plus point is you don't need to learn how to write proto classes. Though you could use protobuf-net for a similar experience. I'm kinda hopeful with CoreWCF, they aim to support more transports (including event gRPC) in the future along with queues other than MSMQ and slowly evolve from being too SOAP specific. There's a lot of potential still for WCF to be a transport agnostic framework that ecompass a lot of transports.
- OpenAPI vs SOAP and WSDL
-
.NET 7 is Available Today
On our end, it's WCF for some servers that haven't been upgraded over. Though it seems we have a path forward for that now with CoreWCF that we're working towards.
-
Bring WCF apps to the latest .NET with CoreWCF and Upgrade Assistant
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...).
- .NET 6 is now in Ubuntu 22.04
-
CoreWCF 1.1.0 release and project templates
It's seems there's already design work started for a generic queue concept here. I'm pretty interested to see how it goes as well as that'll be a big part for CoreWcf to move forward as a viable choice for greenfield projects and not just a way to migrate existing Wcf projects to Core.
-
Questions about OWIN and WCF from a high level.
The ongoing .net core port called CoreWcf plans to realize that goal as a future feature on it's roadmap. Where there's plans on adding new transports that didn't exist on .net framework wcf like Grpc, Azure Service bus, Amazon SQS, rabbitmq etc...
-
CoreWCF v1.0.0 released and comes with official support from Microsoft
If you hit any difficulties or have any problems, feel free to jump on the gitter channel. Details for that are in the repo contributing guide.
runtimelab
-
Is .NET just miles ahead or am I delusional?
There was a "green thread" experiment for dotnet a while ago, here is the conclusion: https://github.com/dotnet/runtimelab/issues/2398
-
Why choose async/await over threads?
Experiment result write-up: https://github.com/dotnet/runtimelab/blob/e69dda51c7d796b812...
TLDR: The green threads experiment was a failure as it found (expected and obvious) issues that the Java applications are now getting to enjoy, joining their Go colleagues, while also requiring breaking changes. It, however, gave inspiration to subsequent re-examination of current async/await implementation and whether it can be improved by moving state machine generation and execution away from IL completely to runtime. It was a massive success as evidenced by preliminary overhead estimations in the results.
-
Garnet – A new remote cache-store from Microsoft Research
Yeah, it kind of is. There are quite a few of experiments that are conducted to see if they show promise in the prototype form and then are taken further for proper integration if they do.
Unfortunately, object stack allocation was not one of them even though DOTNET_JitObjectStackAllocation configuration knob exists today, enabling it makes zero impact as it almost never kicks in. By the end of the experiment[0], it was concluded that before investing effort in this kind of feature becomes profitable given how a lot of C# code is written, there are many other lower hanging fruits.
To contrast this, in continuation to green threads experiment, a runtime handled tasks experiment[1] which moves async state machine handling from IL emitted by Roslyn to special-cased methods and then handling purely in runtime code has been a massive success and is now being worked on to be integrated in one of the future version of .NET (hopefully 10?)
[0] https://github.com/dotnet/runtime/issues/11192
[1] https://github.com/dotnet/runtimelab/blob/feature/async2-exp...
-
Java virtual threads hit with pinning issue
Unlike these folks from dotnet, which tested directly on ASP for real workload
https://github.com/dotnet/runtimelab/issues/2398?darkschemeovr=1
-
Ask HN: Do we have evidence that green threading is faster than OS threads?
[1] https://github.com/dotnet/runtimelab/issues/2398
-
JEP Draft – Derived Record Creation (Preview) – Java
The only way to avoid it is to not build on top of Java or not adding any features on top of Java.
> To give another example with C#, there has been a lot of recent discussion about finding potential alternatives to their async-await concurrency model. They cite the level of effort it takes to maintain the async await style code and the costs that come from this.
I had a very different take-away. They did PoC with virtual threads and decided it's not worth the switch now and async-await that they have is good enough.
https://github.com/dotnet/runtimelab/issues/2398
> Some of the languages it gets compared too aren't even that old yet.
C# is old enough to drink and Scala just had its 20th birthday this week :)
-
.NET 8 – .NET Blog
It was tried and the dotnet team decided to drop it: https://github.com/dotnet/runtimelab/issues/2398
-
.NET Green Thread Experiment Results
Technical details here: https://github.com/dotnet/runtimelab/blob/feature/green-thre...
-
Thread-per-Core
Just last month .NET ended a green threading experiment, mainly because the overhead it adds to FFI was too high:
https://github.com/dotnet/runtimelab/issues/2398
Rust had green threads until late 2014, and they were removed because of their impact on performance.
Everyone has done the basic research: green threading is a convenient abstraction that comes with certain performance trade offs. It doesn't work for the kind of profile that Rust is trying to target.
- Green Thread Experiment Results
What are some alternatives?
SoapCore - SOAP extension for ASP.NET Core
.NET Runtime - .NET is a cross-platform runtime for cloud, mobile, desktop, and IoT apps.
Introducing .NET Multi-platform App UI (MAUI) - .NET MAUI is the .NET Multi-platform App UI, a framework for building native device applications spanning mobile, tablet, and desktop.
DNNE - Prototype native exports for a .NET Assembly.
FrameworkBenchmarks - Source for the TechEmpower Framework Benchmarks project
.NET-Obfuscator - Lists of .NET Obfuscator (Free, Freemium, Paid and Open Source )
dapr - Dapr is a portable, event-driven, runtime for building distributed applications across cloud and edge.
wcf - This repo contains the client-oriented WCF libraries that enable applications built on .NET Core to communicate with WCF services.
csharplang - The official repo for the design of the C# programming language
zeebe-dapr-example - An example that allows to orchestrate Dapr microservices with the Zeebe process engine.
Cocona - Micro-framework for .NET console application. Cocona makes it easy and fast to build console applications on .NET.