You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
IDs are part of the wire and storage contract. Don't reuse or renumber them after deployment. Use <xref:Orleans.AliasAttribute> when a stable serialized type alias is required independently of the CLR name.
34
34
35
+
## Hot Reload for serializable members
36
+
37
+
Enable the Hot Reload generation shape in development builds:
The generator gives serializer and copier fields stable identities and resolves newly added concrete codec and copier dependencies when an existing generated instance first uses them. A running application can therefore apply supported .NET Hot Reload updates which add strongly typed `[Id]` members to `[GenerateSerializer]` classes and records, including members whose concrete serializable type is added in the same update.
46
+
47
+
Keep each `[Id]` value stable and unique. Additive member updates preserve the existing wire contract. Changes to existing member types, IDs, type hierarchy, generic shape, grain interfaces, and generated invokable types follow the corresponding .NET Hot Reload and Orleans contract compatibility requirements. A restart rebuilds the serializer manifest after updates which introduce new types through polymorphic declarations such as `object` or interfaces, or through container element types.
48
+
49
+
When `OrleansHotReload` is unset or `false`, the generator emits readonly fields with eager initialization for normal application builds.
50
+
35
51
## Generate code for external types
36
52
37
53
When a project must generate serializers for accessible types declared elsewhere, use <xref:Orleans.GenerateCodeForDeclaringAssemblyAttribute>:
0 commit comments