Lds.Web.Components 0.130.0

Lds.Web.Components

Lds is Datalogik LDS' framework for .NET web applications: the parts every one of its applications would otherwise write again — a shell and components for Blazor pages, the Result an operation answers with, permissions and who holds them, an audit trail and the store it writes to — shipped as eight packages that share one version. It prescribes no application architecture: an application keeps its own structure and takes the parts it wants.

Package What it is
Lds.Application The technology-blind core: Result and the failure text that words it, permissions and the current user, granted access, the audit trail and the ports its store implements
Lds.Application.FormattedText The formatted-text sanitiser and its rules, apart from the core on weight
Lds.Application.IpAccess The operations that keep the rules of Lds.IpAccess, Datalogik's IP access package — authorized and recorded in the audit trail, apart from the core on weight
Lds.Infrastructure.MongoDb The MongoDB store for the core's ports: the audit trail and granted access
Lds.Infrastructure.Monitor Lds' operational notices sent to Datalogik's Monitor, apart from the core on weight
Lds.Web.Components The Blazor components and their SCSS, with Font Awesome Free and the editors they use
Lds.Web.Components.Testing bUnit/xUnit support for testing pages built on the components
Lds.Web.IpAccess The IP access screens over those operations, apart from the components on weight

The packages are on Datalogik's feed, https://components.datalogik.dk/v3/index.json.

This package

The Blazor components a solution builds its screens from: the shell every page renders inside, the block a page opens with and the panel a section sits in, buttons and dropdowns, the form fields that show and edit (text, dates, times, numbers, choices, type-ahead, check lists, secrets, formatted text, markup, repeated rows), the row list with its filter and sort, key figures and small charts, markers, dialogues and messages, the failure presentation for an operation's Result, the language and colour-mode selectors, and icons named by meaning. None of them carries business meaning: the page gives them its words and its records. Every component carries its own text in English and Danish.

The styling ships as SCSS sources, so a solution sets the variables it wants — its accent first — and compiles. Font Awesome Free, the icon set the glyphs name, ships as a static web asset, and so do the editors the formatted-text and markup fields use.

Getting started

1. Reference the package from the feed above. It brings Lds.Application and Lds.Application.FormattedText with it.

2. Register what only the solution can say, in Program.cs:

builder.Services.AddLocalization();
builder.Services.AddInterfaceLanguages([new("en-GB", "English"), new("da-DK", "Dansk")]);
builder.Services.AddFailureText<MyFailures>();   // the resources a person reads a failure in

builder.Services.AddColourModes();   // optional, each of these
builder.Services.AddDialogues();
builder.Services.AddMessages();

and, with the colour modes, app.MapColourModeSelection();.

3. Write the host document: Bootstrap 5's stylesheet (for its reboot), then the icon set from the package, then the solution's compiled stylesheet:

<html data-bs-theme="@ColourModeCookie.AttributeFor(ColourModeCookie.Read(HttpContext))">
<head>
    <ColourModeResolver />
    <link rel="stylesheet" href="bootstrap/css/bootstrap.min.css" />
    <link rel="stylesheet" href="_content/Lds.Web.Components/font-awesome/css/all.min.css" />
    <link rel="stylesheet" href="css/app.css" />

4. Compile the styles. The package sets the MSBuild property LdsStylesDirectory to its SCSS folder; hand it to the solution's SCSS compiler as a load path and write:

@use "lds" with ($accent: #187c4c, $accent-dark: #25be75);

5. Build a page inside the shell from the components. Using the components shows how, and the repository's workbench shows every component in its states: dotnet run --project samples/Lds.Workbench.

The whole of what a solution supplies — the shell's slots, who is signed in, the audit trail, the render mode — is in Adopting the framework, and this package in detail in The component package.

Documentation, issues and changes

The source, the documents and the issues are on GitHub, at datalogiklds/webframework. The repository is private: if you have access, report a fault or ask for a change there; if you don't, ask Datalogik LDS for it.

  • Adopting the framework — everything a solution supplies to the packages, with the decision behind each item
  • Architecture — how Lds is built and where an application's code meets its types
  • Using the components — how a page is put together from the components
  • Design manual — what the interface looks like and how it behaves
  • Glossary — the words the source and the documents use
  • Changelog — what changed in each version, and what a solution has to change to take it

Showing the top 20 packages that depend on Lds.Web.Components.

Packages Downloads
Lds.Web.IpAccess
The IP access screens of the Lds framework: the Blazor components an administrator keeps Lds.IpAccess's rules with — geo-fencing, the allowed addresses, people's own addresses, the state of the address lists and the access log — over the operations of Lds.Application.IpAccess, with their text in English and Danish.
24
Lds.Web.Components.Testing
Test support for solutions built on Lds.Web.Components: the bUnit setup a component test needs to render inside the shell, a press, any other event and an answer that hold on a busy runner, and a check that every translation is complete. Carries bUnit and xUnit, so it belongs in test projects only.
24
Lds.Web.Components.Testing
Test support for solutions built on Lds.Web.Components: the bUnit setup a component test needs to render inside the shell, a press, any other event and an answer that hold on a busy runner, and a check that every translation is complete. Carries bUnit and xUnit, so it belongs in test projects only.
12
Lds.Web.IpAccess
The IP access screens of the Lds framework: the Blazor components an administrator keeps Lds.IpAccess's rules with — geo-fencing, the allowed addresses, people's own addresses, the state of the address lists and the access log — over the operations of Lds.Application.IpAccess, with their text in English and Danish.
10
Lds.Web.Components.Testing
Test support for solutions built on Lds.Web.Components: the bUnit setup a component test needs to render inside the shell, a press, any other event and an answer that hold on a busy runner, and a check that every translation is complete. Carries bUnit and xUnit, so it belongs in test projects only.
10
Lds.Web.Components.Testing
Test support for solutions built on Lds.Web.Components: the bUnit setup a component test needs to render inside the shell, a press, any other event and an answer that hold on a busy runner, and a check that every translation is complete. Carries bUnit and xUnit, so it belongs in test projects only.
9
Lds.Web.IpAccess
The IP access screens of the Lds framework: the Blazor components an administrator keeps Lds.IpAccess's rules with — geo-fencing, the allowed addresses, people's own addresses, the state of the address lists and the access log — over the operations of Lds.Application.IpAccess, with their text in English and Danish.
9
Lds.Web.Components.Testing
Test support for solutions built on Lds.Web.Components: the bUnit setup a component test needs to render inside the shell, and a check that every translation is complete. Carries bUnit and xUnit, so it belongs in test projects only.
8
Lds.Web.Components.Testing
Test support for solutions built on Lds.Web.Components: the bUnit setup a component test needs to render inside the shell, a press, any other event and an answer that hold on a busy runner, and a check that every translation is complete. Carries bUnit and xUnit, so it belongs in test projects only.
8
Lds.Web.Components.Testing
Test support for solutions built on Lds.Web.Components: the bUnit setup a component test needs to render inside the shell, a press, any other event and an answer that hold on a busy runner, and a check that every translation is complete. Carries bUnit and xUnit, so it belongs in test projects only.
7
Lds.Web.Components.Testing
Test support for solutions built on Lds.Web.Components: the bUnit setup a component test needs to render inside the shell, and a check that every translation is complete. Carries bUnit and xUnit, so it belongs in test projects only.
6
Lds.Web.Components.Testing
Test support for solutions built on Lds.Web.Components: the bUnit setup a component test needs to render inside the shell, a press, any other event and an answer that hold on a busy runner, and a check that every translation is complete. Carries bUnit and xUnit, so it belongs in test projects only.
6
Lds.Web.IpAccess
The IP access screens of the Lds framework: the Blazor components an administrator keeps Lds.IpAccess's rules with — geo-fencing, the allowed addresses, people's own addresses, the state of the address lists and the access log — over the operations of Lds.Application.IpAccess, with their text in English and Danish.
6
Lds.Web.Components.Testing
Test support for solutions built on Lds.Web.Components: the bUnit setup a component test needs to render inside the shell, and a check that every translation is complete. Carries bUnit and xUnit, so it belongs in test projects only.
5
Lds.Web.Components.Testing
Test support for solutions built on Lds.Web.Components: the bUnit setup a component test needs to render inside the shell, a press and an answer that hold on a busy runner, and a check that every translation is complete. Carries bUnit and xUnit, so it belongs in test projects only.
5

.NET 10.0

Version Downloads Last updated
0.146.0 3 2026-11-17
0.145.0 1 2026-11-17
0.144.0 1 2026-11-16
0.143.1 0 2026-11-16
0.143.0 1 2026-11-16
0.142.0 3 2026-11-15
0.141.1 4 2026-11-15
0.141.0 1 2026-11-15
0.140.0 1 2026-11-15
0.139.1 9 2026-11-15
0.139.0 1 2026-11-15
0.138.0 4 2026-11-15
0.137.0 2 2026-11-15
0.136.1 1 2026-11-15
0.136.0 1 2026-11-15
0.135.0 1 2026-11-15
0.134.1 5 2026-11-15
0.134.0 1 2026-11-15
0.133.0 2 2026-11-15
0.132.0 0 2026-11-15
0.131.0 2 2026-11-15
0.130.0 3 2026-11-15
0.129.0 2 2026-11-14
0.128.0 4 2026-11-14
0.127.0 1 2026-11-14
0.126.0 2 2026-11-14
0.125.1 0 2026-11-14
0.125.0 1 2026-11-14
0.124.0 2 2026-11-14
0.123.0 1 2026-11-14
0.122.0 1 2026-11-14
0.121.0 10 2026-11-12
0.120.0 24 2026-11-12
0.119.0 1 2026-11-12
0.118.0 1 2026-11-12
0.117.0 2 2026-11-12
0.116.0 3 2026-11-11
0.115.0 7 2026-11-11
0.113.0 4 2026-11-11
0.112.0 7 2026-11-11
0.111.1 4 2026-11-10
0.111.0 7 2026-11-10
0.110.0 3 2026-11-09
0.109.0 7 2026-11-09
0.108.1 4 2026-11-09
0.108.0 6 2026-11-09
0.107.0 5 2026-11-09
0.106.1 3 2026-11-09
0.106.0 3 2026-11-08
0.105.0 2 2026-11-08
0.104.0 3 2026-11-08
0.103.0 5 2026-11-08
0.102.0 3 2026-11-08
0.101.0 7 2026-11-08
0.100.0 2 2026-11-08
0.99.0 2 2026-11-08
0.98.1 4 2026-11-08
0.98.0 7 2026-11-08
0.97.1 7 2026-11-08
0.97.0 5 2026-11-08
0.96.0 6 2026-11-08