samples VS CoreWCF

What you may have been looking for is these:

- https://learn.microsoft.com/en-us/dotnet/core/deploying/nati...

- https://github.com/dotnet/samples/blob/main/core/nativeaot/N...

Mono has been a stable choice for embedding in game-script style scenarios, in particular, because of the ability to directly call its methods inside providing the caller honors the calling convention correctly, but it has been slowly becoming more of a liability as you are missing out on a lot of performance by not hosting CoreCLR instead, if that is the desired scenario.

For .dll/.so/.dylib's, it is easier and often better to just build a native library with naot instead (you can also produce a statically linkable binaries but it might have issues on e.g. macOS which has...not the most reliable linker that likes to take breaking changes).

After I do my research, I found these examples on dotnet repo. It uses dll instead of apk which is fine, I can still download the extension dll and then load it. But it has restriction of only have one dll for each project and can't be uninstalled. As i said before, tachiyomi only define CSS selector in theme, and then generate apk for each website with its base URL, so there's no way to create project for each website. Is there a way to generate dll for each class that inherits class Parent?

A pointer: https://github.com/dotnet/samples/blob/main/csharp/parallel/ParallelGrep/Program.cs

Just a guess: do you need to set the SelfContained property, maybe? That's the only real difference I can see from the official sample: https://github.com/dotnet/samples/tree/main/core/nativeaot/NativeLibrary

It's really dead? They trying to resurrect it? They added C# and some new samples https://github.com/dotnet/samples/tree/main/framework/windows-workflow-foundation/application/HiringRequestProcess/CS

A comparison on how to reuse code and the differences between .NET IoT and .NET nanoFramework is available here.

Here is sample code

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.