Documentation — Blazor

Comprehensive guides, API reference, and integration patterns for Isabyte Power Tools on Blazor. It's a layered component library targeting the latest .NET, supporting all three Blazor hosting models: Interactive Server, WebAssembly, and hybrid rendering.

Quick Links

Getting Started — install, configure, and render your first component.
Component Demos — live interactive demos with code for every component.
Theme Building — visual theme builder and CSS custom-properties guide.

Architecture

The library is layered:

Your Blazor app  (Server / WebAssembly / Hybrid)
  └─ Isabyte.PowerTools.Components         component library
  │                                        (Controls, Images & Animation, Tools)
  └─ Isabyte.PowerTools.Services           JavaScript interop layer
  │                                        (IJavascriptService: DOM, files, media)
  └─ Isabyte.PowerTools.Components.Common   IsabyteRootComponent (root wrapper + state)

Key Concepts

IJavascriptService — the JS-interop interface (DOM operations, file downloads, clipboard, media capture). Injected automatically when you register Isabyte Power Tools services.
IsabyteRootComponent — a root wrapper that cascades global application state (license status, rendering mode, culture, shared configuration) down the component tree via Blazor's CascadingValue. Parameters marked Cascading are supplied automatically by this ancestor, so descendants read them without prop-drilling.

Runtime & Platforms

Components work across all Blazor rendering modes:

Mode	How it works	Best for
Interactive Server	Runs on the server; UI updates over SignalR	Internal tools, admin panels, sensitive data
WebAssembly	Runs in the browser via the .NET WASM runtime	Public apps, offline-capable scenarios
Hybrid (Auto)	Server-rendered first, switches to WASM after download	Fast first load + full client capability

Note — Some components (IsabyteTerminalClient, IsabyteServerMonitor) need a server connection and are best suited to Interactive Server or Hybrid.

Globalization & Localization

Components respect .NET's CultureInfo for date/time and number formatting and text direction. Eight cultures ship built in — see Globalization & Localization for the list — and the IsabyteLanguage component provides a culture selector that updates and persists the active culture.

Component Reference

For each component's parameters, event callbacks, and related configuration, browse the live component demos — the live reference for every component.