samples VS MSBuild

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

I did get confirmation that the actual kill has been postponed to .Net 9.0 rather than .Net 8.0 . However, that PR is factually wrong regarding when System.Runtime.Serialization use became opt-in -- I had to counter-adjust Rogue Survivor Revived to opt into using System.Runtime.Serialization for .Net 7.0, last November i.e. Nov 2022.

Like this https://github.com/dotnet/msbuild/blob/d0060335c1fb2f0523b1cf4656c464c5c4316783/src/Framework/NativeMethods.cs

Here is a taste of what to expect: https://github.com/dotnet/msbuild

The main thing they do is to list projects so that you can open a solution and see a set of projects, or build a solution and build everything there. They also give a lot of customization and fortunately it's rare that you need to know anything about that. It does feel somewhat unnecessary since you should be able to open a project with its dependencies. Hopefully solution files are going to be cleaned up: https://github.com/dotnet/msbuild/issues/1730

Since the previous check, the project has grown a lot. Our analyzer has become more advanced, too. This only makes this task more interesting! Despite the high quality of the MSBuild product and the well-known name of its creator, we again managed to find some issues in MSBuild's source code. The project is almost entirely written in C#. You can see it on GitHub. We took the code from this commit.

relevant github issue: https://github.com/dotnet/msbuild/issues/1730

msbuild is the "make" system, but for .Net. Those .csproj files are just makefiles by another name. Also, msbuild is not Windows-only. The readme specifically states that it can run on Unix (and Unix-like) systems that support .Net Core.

You can't do without source files when you want to better understand what is happening "under the hood" of a particular system. For example, do you want to improve your understanding of how types from the standard library work? The source code of .NET Framework and .NET will help you to do that. Do you want to dig deeper into the compiler? No problem - here is the Roslyn's source code at your service. Do you need to look inside the build system? Here you go - the MSBuild code is also open-source. By the way, if you are interested in build processes, you may also find MSBuild Structured Log Viewer useful. It's a tool that allows you to work with MSBuild build logs in a convenient format.