Overview

Comprehensive guides, API reference, and integration patterns for Blazor Power Tools.

Architecture Overview

Blazor Power Tools is a layered component library targeting the latest .NET. It supports all three Blazor hosting models: Interactive Server, WebAssembly, and hybrid rendering.

┌─────────────────────────────────────────────┐
│  Your Blazor application                    │
│  (Server, WebAssembly, or hybrid)           │
└──────────────────┬──────────────────────────┘
                   │
┌──────────────────▼──────────────────────────┐
│  Isabyte.PowerTools.Blazor                  │
│  Razor component library                    │
│  - Controls (forms, inputs, selectors)      │
│  - Charts & data (grid, 15+ chart types)    │
│  - Images & animation (WebGL, canvas)       │
│  - Tools (terminal, monitor, editors)       │
└──────────────────┬──────────────────────────┘
                   │
┌──────────────────▼──────────────────────────┐
│  Isabyte.PowerTools.Services                │
│  JavaScript interop layer                   │
│  - DOM, file handling, media capture        │
└──────────────────┬──────────────────────────┘
                   │
┌──────────────────▼──────────────────────────┐
│  Isabyte.PowerTools.Components.Common       │
│  - IsabyteRootComponent (root + state)      │
│  - IsabyteRootComponentBase                 │
└─────────────────────────────────────────────┘

Key Building Blocks

IJavascriptService — the primary JS interop interface. Handles DOM operations, file downloads, clipboard access, media capture, and browser API calls. Injected automatically once you register the Isabyte services.

IsabyteRootComponent — the root wrapper that cascades global application state through the component tree: license validation, render-mode detection, culture settings, and shared configuration every component can read.

Razor parameters and EventCallbacks — every component is configured with ordinary [Parameter] values and raises EventCallback<T>, so binding syntax (@bind-Value) and .razor tooling work exactly as they do for your own components.

Next Steps

• Getting Started — install the package and render your first component.
• Package Setup — registry configuration, credentials, and version pinning.
• Theme Building — match your brand's colors and styling.
• API Reference — every component with its properties and events.
• Browse the live component demos to see each one running.