.NET Runtime VS CoreWCF

Compare .NET Runtime vs CoreWCF and see what are their differences.

.NET Runtime

.NET is a cross-platform runtime for cloud, mobile, desktop, and IoT apps. (by dotnet)

CoreWCF

Main repository for the Core WCF project (by CoreWCF)
Our great sponsors
  • Smarter Code - Your Free Guide to Become Microsoft Azure Certified
  • Nanos - Run Linux Software Faster and Safer than Linux with Unikernels
  • Scout APM - A developer's best friend. Try free for 14-days
.NET Runtime CoreWCF
223 9
7,614 993
4.2% 1.9%
10.0 8.3
4 days ago 4 days ago
C# C#
GNU General Public License v3.0 or later MIT License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.

.NET Runtime

Posts with mentions or reviews of .NET Runtime. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-11-24.

CoreWCF

Posts with mentions or reviews of CoreWCF. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-11-08.
  • Welcome to C# 10
    1 project | reddit.com/r/programming | 9 Nov 2021
    We have some WCF services here, no migration path at the moment without big rewrites... Hopefully once CoreWCF is stable, we'll be able to finally upgrade those services someday.
  • Announcing .NET 6 — The Fastest .NET Yet
    9 projects | reddit.com/r/programming | 8 Nov 2021
    There's Core WCF at least if you have existing services as a migration path. We're waiting for it to have a stable release and check if it supports all the bindings we need so we can move some of our WCF services to .Net6+.
  • Calling WCF services from .NET Core clients
    2 projects | dev.to | 11 Oct 2021
    We already discussed some high-level architectural approaches to integrate systems. But we didn’t touch upon the data exchange between monolith and microservice consumers: we could post complete object feed onto a message queue, but that’s not always fit for purpose as messages should be lightweight. Another way (keeping in mind our initial WCF premise), we could call the services as needed and make alterations inside microservices. And Core WCF is a fantastic way to do that. If only we used all stock standard service code.
  • Microservices with .NET 5
    5 projects | reddit.com/r/dotnet | 28 May 2021
    It may come back alive once CoreWCF get's to GA.
  • C# 9 top-level programs and target-typed expressions
    11 projects | news.ycombinator.com | 30 Mar 2021
    You may want to keep an eye on CoreWCF: https://github.com/CoreWCF/CoreWCF

    Though as a heavy WCF user in the past, I'd suggest your best bet is simply to throw out all your binding configs, and build your own REST API or similar backend (gRPC support in .NET 5+ is something often also recommended if you want something more RPC-like and need/want a more binary-serializer like approach, though in 2021 I'd just use JSON and something REST-ish myself). The nice thing about the Interface-driven "contract" approach should be that implementing your own is just a matter of implementing all your contract interfaces and injecting the physical implementations yourself.

    I realize that can be easier said than done as things accidentally got coupled to very specific styles of bindings over the years and not everyone followed best practices and used the Async contracts so you have to tear out a bunch of synchronous faking code and wire back in Task/ValueTask. But generally, overall, the process was implement the interfaces and remove the "magic" in the process and I often found you end up with something better anyway because it is simpler and prone to less "magic" failures.

  • .NET roadmap
    2 projects | reddit.com/r/csharp | 10 Mar 2021
    Then what's this?
  • Transitioning from WCF
    2 projects | reddit.com/r/csharp | 1 Mar 2021
  • Azure Active Directory reduced core count from ~40k to ~20k by migrating to .NET Core 3.1
    9 projects | reddit.com/r/programming | 14 Jan 2021
    You might want to check https://github.com/dotnet/wcf and https://github.com/CoreWCF/CoreWCF
  • .NET WCF vs NodeJS for backend
    1 project | reddit.com/r/learnprogramming | 24 Dec 2020
    In addition, many features of WCF are not well-supported on .NET Core and (and, now, .NET 5) because Microsoft decided to not officially support server-side WCF on the cross-platform version of the .NET framework (much to the angst of many WCF developers.) There is an open-source, not-officially-supported-by-Microsoft version of WCF that you can get running on the cross-platform versions of .NET, but it's still early and lacking quite a few features.

What are some alternatives?

When comparing .NET Runtime and CoreWCF you can also consider the following projects:

Ryujinx - Experimental Nintendo Switch Emulator written in C#

actix-web - Actix Web is a powerful, pragmatic, and extremely fast web framework for Rust.

ASP.NET Core - ASP.NET Core is a cross-platform .NET framework for building modern cloud-based web applications on Windows, Mac, or Linux.

vgpu_unlock - Unlock vGPU functionality for consumer grade GPUs.

runtimelab - This repo is for experimentation and exploring new ideas that may or may not make it into the main dotnet/runtime repo.

awesome-blazor - Resources for Blazor, a .NET web framework using C#/Razor and HTML that runs in the browser with WebAssembly.

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.

SharpLab - .NET language playground

CoreCLR - CoreCLR is the runtime for .NET Core. It includes the garbage collector, JIT compiler, primitive data types and low-level classes.

zeebe-dapr-example - An example that allows to orchestrate Dapr microservices with the Zeebe process engine.

HomeBrew - 🍺 The missing package manager for macOS (or Linux)