iot VS samples

On the other hand, for maximum code reuse, you can use regular .NET 7, plus .NET IoT Libraries if you need sensors/access to GPIO and so on, plus Avalonia as a GUI, which is also using XAML, but incompatible with UWP.

Try the same program but with a hardware PWM library, e.g. https://pypi.org/project/rpi-hardware-pwm/

.NET nanoFramework has support for GPIO, I2C, SPI, PWM, ADC, DAC, Serial, 1-Wire. Also the API are aligned with .NET IoT making it easy for code reuse between development on a Raspberry Pi with .NET 6.0 and an MCU running .NET nanoFramework.

You can write machine learning application using C# with the help of https://dotnet.microsoft.com/en-us/apps/machinelearning-ai/ml-dotnet. Additionally IoT development as well using C# (https://github.com/dotnet/iot/tree/main/samples/force-sensitive-resistor)

Every sensor and module out there woks with on of the standard protocols like I2C or SPI and C# supports them. But everyone wants pre-made libraries/device binding and dealing with raw I2C and SPI is frustrating. .NET also has device binding libraries and most popular devices have binding there. Meadow team is also porting their binding to Linux.

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