Kouji Matsui

In my first inspiration for IL2C's idea: "Why does it required a lot of cost in this case? What different between C language and C# (or CIL)? And/or why couldn't...

### Other topic (only listed) * Switch from Azure DevOps Pipelines to GitHub Actions. * Automated building script on host == target environment. * ex: Build csproj on Windows, IL2C...

NOTE: Add platform targets applying only IL2C bulding time, NOT IL2C runtimes.

Azure DevOps Pipelines will break.

ILSupport couldn't execute on posix environment, because it depends native tooling `ilasm` and `ildasm` on netfx distribution.

Another solution: [InlineIL.Fody](https://github.com/ltrzesniewski/InlineIL.Fody) * How to automatic convert from ILSupport's pure IL assembler source code to InlineIL.Fody operators. * Maybe have to write mini onetime utility for generate InlineIL.Fody operator...

Migration code fragment is [here.](https://github.com/kekyo/IL2C.InlineIL-Migration)

@am11 Thank you, your opinion is right. I agreed MVP requirement has to make smaller, but I think: * IL2C is AOT translation, that means verification and problem insight is...

Topic on IL SDK: I checked [IL SDK NuGet package](https://www.nuget.org/packages/Microsoft.NET.Sdk.IL/) and got another solution. It contains referrer of ILAsm/ILDasm .NET 5.0 based binaries splitted [several public distributed NuGet sub packages](https://github.com/dotnet/runtime/blob/57bfe474518ab5b7cfe6bf7424a79ce3af9d6657/src/coreclr/.nuget/Microsoft.NET.Sdk.IL/targets/Microsoft.NET.Sdk.IL.targets#L54)....

Memoized ILAsm native binary naming rules: * [For windows x64](https://www.nuget.org/packages/runtime.win-x64.Microsoft.NETCore.ILAsm/): runtime.win-x64.Microsoft.NETCore.ILAsm * [For linux x64](https://www.nuget.org/packages/runtime.linux-x64.Microsoft.NETCore.ILAsm/): runtime.linux-x64.Microsoft.NETCore.ILAsm