Native AOT

Friflo.Engine.ECS supports Native AOT deployment.

Note JSON serialization is currently not support by Native AOT.

Using Friflo.Engine.ECS does not require a source generator - aka Roslyn Analyzer. A source generator could be used to register component types automatically.

Because of this component types used by an application must be registered on startup as shown below.

var aot = new NativeAOT();
aot.RegisterComponent<MyComponent>();
aot.RegisterTag      <MyTag1>();
aot.RegisterScript   <MyScript>();
var schema = aot.CreateSchema();

In case using an unregistered component a TypeInitializationException will be thrown. E.g.

 entity.AddComponent(new UnregisteredComponent());

On console to the exception log looks like

A type initializer threw an exception. To determine which type, inspect the InnerException's StackTrace property.
Stack Trace:
   at System.Runtime.CompilerServices.ClassConstructorRunner.EnsureClassConstructorRun(StaticClassConstructionContext*) + 0x14f
   at System.Runtime.CompilerServices.ClassConstructorRunner.CheckStaticClassConstructionReturnNonGCStaticBase(StaticClassConstructionContext*, IntPtr) + 0x1c
   at Friflo.Engine.ECS.Entity.AddComponent[T](T&) + 0x4e
   at MyApplication.UseUnregisteredComponent() + 0x7c

Other Trimmings issues

Community feedback on Discord. In case you get an exception like:

System.IndexOutOfRangeException: Index was outside the bounds of the array.
 Stack Trace:
   at Friflo.Engine.ECS.Relations.AbstractEntityRelations.GetEntityRelations(EntityStoreBase, Int32) + 0xd5
   at Friflo.Engine.ECS.Relations.AbstractEntityRelations.AddRelation[TRelation](EntityStoreBase, Int32, TRelation&)
   ...

Add the <TrimmerRootAssembly> to your *.csproj. See: Trimming options > Root assemblies

<ItemGroup>
  <TrimmerRootAssembly Include="Friflo.Engine.ECS" />
</ItemGroup>