mcpField
S
syncfusion-blazor-license

syncfusion-blazor-license

github.com/syncfusionDevelopment4392 installsUpdated 1w ago
Repository

About syncfusion-blazor-license

A guidance skill for generating, registering, securing, and troubleshooting Syncfusion license keys in Blazor projects. It covers Server, WebAssembly, Auto, Razor Class Libraries, and CI/CD validation, with emphasis on version and platform matching and key confidentiality.

Key features

  1. 01Generate paid, trial, or temporary keys
  2. 02Register keys across Blazor project types
  3. 03Handle WebAssembly keys securely
  4. 04Validate licenses in CI/CD pipelines
  5. 05Troubleshoot license and version errors

Use cases

  1. 01Configure Syncfusion licensing in a Blazor project
  2. 02Avoid exposing keys in WebAssembly client code
  3. 03Validate licenses in Azure Pipelines or GitHub Actions

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/syncfusion/blazor-ui-components-skills --skill syncfusion-blazor-license

After installing, type/syncfusion-blazor-licensein Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
license-registration.md
syncfusion-blazor-web-installer-download.md
syncfusion-blazor-web-installer-install.md

Details

From the project README

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.cs or 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

Troubleshooting license errors
FAQ

Comments

Markdown supported