[feat] Supports AOT publishing

[pelva]

Problem to solve

If the project is published with AOT, you need to add TrimmerRootAssembly entries for all referenced libraries, for example:

<ItemGroup>
    <TrimmerRootAssembly Include="CanKit.Abstractions" />
    <TrimmerRootAssembly Include="CanKit.Adapter.ZLG" />
    <TrimmerRootAssembly Include="CanKit.Adapter.PCAN" />
    <TrimmerRootAssembly Include="CanKit.Adapter.Kvaser" />
    <TrimmerRootAssembly Include="CanKit.Core" />
</ItemGroup>

This significantly increases the size of the compiled executable. Is it convenient to support AOT publishing?

支持aot发布。 如果项目以aot发布需要添加TrimmerRootAssembly ，所有引用的库都要添加，例如

<ItemGroup>
    <TrimmerRootAssembly Include="CanKit.Abstractions" />
    <TrimmerRootAssembly Include="CanKit.Adapter.ZLG" />
    <TrimmerRootAssembly Include="CanKit.Adapter.PCAN" />
    <TrimmerRootAssembly Include="CanKit.Adapter.Kvaser" />
    <TrimmerRootAssembly Include="CanKit.Core" />
  </ItemGroup> 

，这使得编译后的exe体积增大不少 ， 方便支持AOT发布吗

Proposal

For AOT publishing, TrimmerRootAssembly does not need to be added, which helps reduce the executable size.

Alternatives considered

No response

Areas

• Core
• PCAN
• Kvaser
• SocketCAN
• ZLG
• Docs

[pkuyo]

感谢反馈。我考虑的话应该可以将注册机制从反射改为生成注册代码：

• 每个 Adapter 提供统一的静态注册入口，例如 CanKitRegistration.Register()；
• CanKit.Core.targets 根据项目引用，在最终应用中生成强类型注册调用；

构建时会生成类似代码：

using System.Runtime.CompilerServices;

namespace CanKit.Core.Internal;

internal static class CanKitModuleInitializer
{
    [ModuleInitializer]
    internal static void Initialize()
    {
        global::CanKit.Adapter.PCAN.CanKitRegistration.Register();
        global::CanKit.Adapter.ZLG.CanKitRegistration.Register();
    }
}

这样 NativeAOT 可以追踪实际使用的类型就不需要全部保留了可以删除对整个 Adapter 程序集的 preserve="all"。
修改前后的使用方式保持不变。