Kododo.Way.Shell 2.1.1

dotnet add package Kododo.Way.Shell --version 2.1.1
                    
NuGet\Install-Package Kododo.Way.Shell -Version 2.1.1
                    
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Kododo.Way.Shell" Version="2.1.1" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="Kododo.Way.Shell" Version="2.1.1" />
                    
Directory.Packages.props
<PackageReference Include="Kododo.Way.Shell" />
                    
Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.
paket add Kododo.Way.Shell --version 2.1.1
                    
#r "nuget: Kododo.Way.Shell, 2.1.1"
                    
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
#:package Kododo.Way.Shell@2.1.1
                    
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package.
#addin nuget:?package=Kododo.Way.Shell&version=2.1.1
                    
Install as a Cake Addin
#tool nuget:?package=Kododo.Way.Shell&version=2.1.1
                    
Install as a Cake Tool

Kododo.Way.Shell

Shared UI shell for the Kododo Way libraries (ConfigWay, CultureWay, RunWay), from version 2.0 of each.

  • One Way in an app: the Way looks and works as before (app.UseConfigWay("/config")), but its layout, theme, language and session handling come from the shell.
  • Several Ways in an app: an optional panel (for example /admin) with navigation between all of them, one theme and one signed-in user.
  • One React and MUI in an app: the shell serves the shared libraries once, through an import map, to every Way.

In an app

Way libraries register the shell themselves. Configure it and add the panel when you want one:

builder.Services.AddWayShell(o =>
{
    o.Title = "Acme admin";
    o.HomeUrl = "/";
    o.Links.Add(new ShellLink("Docs", "/docs"));
    o.User = ctx => ctx.User.Identity?.IsAuthenticated == true
        ? new ShellUser(ctx.User.Identity.Name!) { SignOutUrl = "/logout" }
        : null;
});

app.UseConfigWay("/config").RequireAuthorization("Admin");
app.UseCultureWay("/translations").RequireAuthorization();
app.UseWayShell("/admin").RequireAuthorization();   // lists the Ways the user may open

The panel can also be the app's home page, app.UseWayShell("/"): it answers only at / itself, so every other address stays the app's. ShellOptions.Notice shows a note above every Way (for example on a public demo), and a Way with IsHidden = true opens in the panel without an item in its menu, e.g. an account page the user's name links to (AccountUrl = "~/#/account/").

Outside the Development environment a Way or the panel answers 403 until you decide on its authorization: RequireAuthorization(...), AllowAnonymous(), a fallback policy, or ShellOptions.AllowAnonymous for public demos. Undecided ones are reported in the log at startup.

In a Way library

public static RouteGroupBuilder UseMyWay(this IEndpointRouteBuilder endpoints, string path = "/my")
{
    var group = endpoints.MapWay(new WayModule("my", "My Way", typeof(MyWay).Assembly, "SPA/dist"), path);
    group.MapGroup("/api").MapRequests(typeof(MyWay).Assembly);   // the shell gives the module {path}/api as apiBase
    return group;
}

The module (SPA/dist/way.js, way.css) is built with the @kododo-dev/way-shell npm package of the same version and embedded with <GenerateEmbeddedFilesManifest>true</GenerateEmbeddedFilesManifest>.

License

MIT

Product Compatible and additional computed target framework versions.
.NET net8.0 is compatible.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed.  net9.0 is compatible.  net9.0-android was computed.  net9.0-browser was computed.  net9.0-ios was computed.  net9.0-maccatalyst was computed.  net9.0-macos was computed.  net9.0-tvos was computed.  net9.0-windows was computed.  net10.0 is compatible.  net10.0-android was computed.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-maccatalyst was computed.  net10.0-macos was computed.  net10.0-tvos was computed.  net10.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (3)

Showing the top 3 NuGet packages that depend on Kododo.Way.Shell:

Package Downloads
Kododo.ConfigWay.UI

Embedded web UI for ConfigWay. Adds a React-based editor served directly from the host application, in Way.Shell — no separate deployment required.

Kododo.CultureWay.UI

Embedded web UI for CultureWay. Adds a React-based localization editor served directly from the host application, so no separate deployment is needed.

Kododo.RunWay.Dashboard

Embedded web dashboard for RunWay. Inspect job statuses, audit timelines, and runner health directly from your ASP.NET Core application.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
2.1.1 88 10/17/2026
2.1.0 84 10/17/2026
2.0.0 140 10/17/2026
2.0.0-preview.2 80 10/17/2026
2.0.0-preview.1 67 10/17/2026