👁 Image
Nabs.Launchpad.Core.Context 10.0.249

👁 NuGet

Nabs.Launchpad.Core.Context

Nabs.Launchpad.Core.Context centralizes user, tenant, and portal context objects so cross-service behavior stays consistent.

Installation

dotnet add package Nabs.Launchpad.Core.Context

The Problem

// 1) User metadata copied between layers
var userId = http.User.FindFirst("oid")?.Value;

// 2) Tenant and portal configuration passed as untyped dictionaries
Dictionary<string, object> context = new();

// 3) Orleans request metadata becomes ad-hoc string keys
RequestContext.Set("usr", value);

Features

• Typed context models (UserContext, TenantContext, PortalContext)
• Navigation definitions via NavigationItem
• Orleans-friendly helpers through UserContextExtensions

Usage

var portal = new PortalContext
{
 PortalName = "admin",
 PortalDisplayName = "Admin Portal",
 PortalBasePath = "/admin"
};

var user = new UserContext
{
 IsAuthenticated = true,
 ObjectId = "user-123",
 DisplayName = "Taylor"
};

Configuration

Register context objects in DI with the lifetime expected by your app (singleton for portal metadata, scoped for user state).

Project Structure

• PortalContext.cs - portal metadata and navigation state
• UserContext.cs / TenantContext.cs - request-level context models
• UserContextExtensions.cs - Orleans context access helpers

License

Copyright (c) Net Advantage Business Solutions.