bundling VS CoreWCF

According to your explanation, it seems this pretty much matches what you're looking for. Although this particular one happens to be an ASP.NET MVC project, the setup works with Razor Pages exactly the same way.

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.

I created a .NET bundler library for exactly this purpose: to provide a migration path for .NET Framework projects which was built with System.Web.Optimization.

You may check out this library as well. I created it exactly with the goal of getting rid of JS-based tools in my .NET projects.

I happen to be the author of such a library. The project contains a fully set up template for RazorPages, which use LibMan, SCSS and ES6 module bundling. It can bundle your assets at build-time (à la webpack) or at run-time (like the bundler of the classic ASP.NET). I find the latter usually more convenient.

CoreWCF might be of some use.

You can open a discussion in the CoreWCF repo:

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.

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.

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

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.

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.