tye VS CoreWCF

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.

I would like to build modules, either in a modular monolith style, or in a microservice style using DAPR and/or Tye.

GitHub: https://github.com/dotnet/tye

I think it's a good option or docker compose with your services only. Maybe check out project tye. Although it seems abandoned.

https://github.com/dotnet/tye for starting up many services/projects and tying them all together

Docker, and check out also Tye https://github.com/dotnet/tye

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

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.

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.

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...).

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...

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.

Site URL Website https://corewcf.net/ Source Code https://github.com/CoreWCF/CoreWCF Announcements https://github.com/CoreWCF/announcements

WCF is part way there too via CoreWCF: https://github.com/CoreWCF/CoreWCF

Did you look at this project? It seems well maintained: https://github.com/CoreWCF/CoreWCF

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+.