Learning Resources

Tutorials, guides, and community resources to help you master Blazor Power Tools.

Home / Docs / Learning

Recommended Learning Path

New to Blazor Power Tools? Follow this path to get productive quickly:

Tutorials

Blazor Fundamentals

New to Blazor itself? These Microsoft resources are excellent starting points:

Blazor Documentation

The official Microsoft docs cover everything from project setup to advanced rendering scenarios.

Microsoft Learn
Blazor Rendering Modes

Understand Server, WebAssembly, and Auto rendering modes — crucial for deciding which BPT components to use where.

Render Modes
JavaScript Interop

Learn how JS interop works in Blazor — the foundation BPT uses for WebGL effects, terminal emulation, and DOM operations.

JS Interop Guide

Frequently Asked Questions

Which .NET version do I need?

Blazor Power Tools targets .NET 10.0. You need the .NET 10 SDK or later.

Does BPT work with Blazor WebAssembly?

Yes. All UI components work in both Server and WebAssembly modes. Some tools (BptTerminalClient, BptServerMonitor) require a server connection and work best in Interactive Server or Hybrid mode.

Can I use BPT with an existing CSS framework like Bootstrap?

Yes. BPT components use their own scoped CSS custom properties and don't conflict with Bootstrap, Tailwind, or other frameworks. You can use them side by side.

How do I update to a new BPT version?

Run dotnet list package --outdated to check for updates, then dotnet add package BlazorPowerTools to install the latest version. Check the changelog for any breaking changes between versions.

Do I need a license for development?

BPT works in development mode without a license key, but components will display a small watermark. Add a license key to remove it. See License Key Setup.


An unhandled error has occurred. Reload 🗙

Rejoining the server...

Rejoin failed... trying again in seconds.

Failed to rejoin.
Please retry or reload the page.

The session has been paused by the server.

Failed to resume the session.
Please reload the page.