Skip to content
Project referenceDevelopmentEngine ccf7d03f
Authored
  • Explicit module sources, dependency closures, catalog candidates and the shared generation owner.

This Foundation layer owns module identities, catalog snapshots, dependency ordering and candidate transactions. It accepts code through explicit source contracts. Dynamic loading, reflection and shadow-copy storage belong to the selected adapter, not ModuleHost.

Use module sources and participants for composition and generation publication for commit/rollback and admission.

Creating a host transfers ownership of the required assembly catalog source. The composition separately selects a matching type metadata source. External assembly registration does not transfer the caller’s ultimate code lifetime. Static code must not be reported as collectible.

Source preflight declares the complete owned assembly names, upstream module dependencies and domain/scope classifications. Preparation receives a frozen candidate closure and returns a complete unpublished contribution. Failed acquisition must retire acquired resources and register any outstanding non-owning probe with the shared gate.

Participants prepare full derived state and expose reversible activation, cleanup-only completion and rollback. A recoverable candidate failure preserves last-good state only after successful compensation. Cleanup/rollback failure closes the generation gate; pending retirement retains owners and dependent transactions.

Reload contexts and snapshots hold live generation references and belong only to the transaction or protected operation. An unload return value is a probe, not successful retirement. Retire feature registries and type-derived state before the module host; no repeated refresh or disposal can reset a terminal fault.

Module handles identify runtime transactions, while module information is non-owning diagnostics. Foundation does not require a dynamic-loader cache directory or choose a process-wide source implicitly.

Browse the exact type and member contracts in the selected CLR surface. Declaration coverage does not certify runtime or collectible-unload behavior.

Project: Inno.Extensibility.Modules
Source: src/foundation/extensibility/Inno.Extensibility.Modules/Inno.Extensibility.Modules.csproj

Type API Description
AssemblyCatalogSnapshot engine Represents an immutable view of the assemblies participating in one catalog generation.
AssemblyDomain engine Identifies the ownership and reload boundary of a managed assembly.
AssemblyExtensions engine Provides ownership and scope metadata helpers for assemblies participating in the Inno runtime.
AssemblyModuleHandle engine Identifies a logical assembly module without retaining its runtime assemblies.
AssemblyModuleInfo engine Provides non-owning diagnostic information about an active assembly module.
AssemblyModuleStatus engine Describes the catalog state of a published assembly module generation.
AssemblyReloadContext engine Provides assembly catalogs and participant-specific state during a reload transaction.
AssemblyReloadSession engine Controls activation, completion, and rollback of one prepared module generation.
AssemblyScope engine Identifies whether an assembly can participate in runtime or editor-only dependency graphs.
IAssemblyCatalogParticipant engine Builds transactional derived state for an assembly catalog generation.
IAssemblyCatalogSource engine Owns the host assembly source independently of any module loading implementation.
IAssemblyCatalogTransaction engine Controls one participant’s prepared state during an assembly catalog transaction.
IModuleLifetime engine Owns implementation-specific resources acquired for one unpublished or active module generation.
IModuleSource engine Prepares one module generation without publishing it to the owning catalog.
ModuleAssemblyDescriptor engine Describes the ownership classification of one planned assembly without loading its code.
ModuleCatalogContribution engine Freezes the assemblies, classification and lifetime of one acquired module generation.
ModuleHost engine Owns the active managed assembly catalog and transactional module generations.
ModuleHostOptions engine Selects the isolated host catalog without prescribing storage for contributed module sources.
ModuleSourceContext engine Supplies a source with the frozen dependencies and retirement boundary of one candidate generation.