tye
CoreWCF
Our great sponsors
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.
tye
-
How to configure true dependency injection in System.CommandLine
System.CommandLine is the official .NET library that provides common functionality for command-line applications. This includes features like argument parsing, automatic help text generation, tab autocomplete, suggestions, corrections, sub-commands, user cancellation, and much more. Many official .NET tools are built on top of System.CommandLine, including the .NET CLI, Kiota, Tye, numerous Azure tools, and other .NET additional tools.
-
Modular Architecture Design question | Re-using modules in multiple applications
I would like to build modules, either in a modular monolith style, or in a microservice style using DAPR and/or Tye.
-
How many of you run your application services locally?
GitHub: https://github.com/dotnet/tye
-
Docker-compose vs bridge to kubernetes for local development with debugging
I think it's a good option or docker compose with your services only. Maybe check out project tye. Although it seems abandoned.
-
Good nuget packages or GitHub repos to check out?
https://github.com/dotnet/tye for starting up many services/projects and tying them all together
-
The complexity of launching local environment
Docker, and check out also Tye https://github.com/dotnet/tye
- Start Podman on WSL2 in 4 steps
-
Local iis vs docker env, pros and cons?
Or start all five with one command using https://github.com/dotnet/tye ! Same idea. Less typing.
You should use project tye. It was built for this use case. You can spin up all 5 with a single command. As if you ran dotnet watch run on each. You can add sql server or elastic search pretty easily. It works with webpack projects but is a bit janky. We use it to spin up 3 .net web apps, a react frontend, sql and elastic. All with a single command. https://github.com/dotnet/tye
-
Why Microsoft itself doesn't use Blazor?
The dotnet team at least does use it in a number of stuff. Tye's dashboard UI uses Blazor server, and if I recall some parts of MS docs uses Blazor WASM to evaluate C# code in the browser. dotnet live and https://themesof.net/ uses Blazor server as well.
CoreWCF
-
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
-
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
-
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.
-
Modern WCF: Running CoreWCF in a Linux App Service
Site URL Website https://corewcf.net/ Source Code https://github.com/CoreWCF/CoreWCF Announcements https://github.com/CoreWCF/announcements
-
20 years of .NET: Reflecting on Microsoft's not-Java
WCF is part way there too via CoreWCF: https://github.com/CoreWCF/CoreWCF
-
.NET Framework 4.8 and .NET 6
Did you look at this project? It seems well maintained: https://github.com/CoreWCF/CoreWCF
-
Announcing .NET 6 — The Fastest .NET Yet
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+.
What are some alternatives?
SoapCore - SOAP extension for ASP.NET Core
dapr - Dapr is a portable, event-driven, runtime for building distributed applications across cloud and edge.
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.
draft - A tool for developers to create cloud-native applications on Kubernetes.
FrameworkBenchmarks - Source for the TechEmpower Framework Benchmarks project
okteto - Develop your applications directly in your Kubernetes Cluster
wcf - This repo contains the client-oriented WCF libraries that enable applications built on .NET Core to communicate with WCF services.
zeebe-dapr-example - An example that allows to orchestrate Dapr microservices with the Zeebe process engine.
.NET Runtime - .NET is a cross-platform runtime for cloud, mobile, desktop, and IoT apps.
runtimelab - This repo is for experimentation and exploring new ideas that may or may not make it into the main dotnet/runtime repo.
MagicOnion - Unified Realtime/API framework for .NET platform and Unity.