Intended use

What it is for

The ECS Shell is the host application of the External Configuration Server UI. It owns shared chrome (nav, layout), the OIDC session, and routes users into the ECS micro-frontends (Admin, Monitoring, Self-Service) by embedding them in iframes from configuration.

Use it when

• You are assembling the ECS UI and need a single shell that composes the ECS MFEs.
• You want config-driven MFE registration via the MicroFrontends section rather than hard-coded references.

Do not use it for

• A dotnet new scaffold today - there is no manifest (see repo status).
• ECS domain features (config CRUD, monitoring, self-service) - those live in the dedicated MFEs.

Composition model

MicroFrontendPlaceholder resolves the requested MFE by longest path prefix and builds an iframe URL from each entry's BaseUrl/Path. Today the sample config registers generic placeholders (AIChat, Logistics) rather than the ECS Admin/Monitoring/Self-Service MFEs - update MicroFrontends to point at them.

See also

• Solution structure
• Development
• ECS Admin MFE