Syncfusion Blazor License Configuration
Manage Syncfusion Blazor license keys across all Blazor project types - Server, WebAssembly, Auto, and Razor Class Libraries.
When to Use
Use this skill when you need to:
- Generate a Syncfusion license key (paid, trial, or temporary)
- Register a license key in any Blazor project type
- Secure license keys in Blazor WebAssembly projects (avoid browser exposure)
- Validate licenses in CI/CD pipelines (Azure Pipelines, GitHub Actions, Jenkins)
- Troubleshoot license errors — trial banner, invalid key, platform or version mismatch
Do NOT use for:
- Initial Blazor project setup → use
syncfusion-blazor-common
Key Rules
- Version Specific: License keys are version-specific for the Syncfusion platform
- Platform Specific: Different keys for different platforms (Blazor, ASP.NET, etc.)
- WASM Security: Never register license keys in client-side Blazor WebAssembly
Program.cs— use licensed NuGet packages instead - Confidentiality: License keys are secrets. Never share or commit them to source
Common Scenarios
Generate a license key
Register a license key
Razor Class Library with Syncfusion Blazor components
Blazor WebAssembly app (security concern)
Security Warning (WASM): Do NOT register license keys in client-side Blazor WebAssembly
Program.csor commit keys into source. Client-side assemblies are downloadable and can expose license keys to end users. Treat license keys like secrets.
⚠️ Do NOT register keys in client-side code. See secure deployment options:
Recommended: Use licensed NuGet packages instead