# Syncfusion for ASP.NET Core — agent index Source: https://ai.syncfusion.com/aspnet-core/llms.txt Canonical: https://ai.syncfusion.com/aspnet-core/llms.txt Entry-point: https://ai.syncfusion.com/llms.txt Essential-Studio-release: 2026 Volume 2 (v34.1.29) Applies-to: ASP.NET Core Family: .NET Web Host-skill-pack: syncfusion/aspnetcore-ui-components-skills Skills-in-pack: 67 Reference-files-in-pack: 973 Packages: `Syncfusion.EJ2.AspNet.Core` on NuGet Documentation-root: https://ej2.syncfusion.com/aspnetcore/documentation/introduction License-registration: https://ej2.syncfusion.com/aspnetcore/documentation/licensing/how-to-register-in-an-application MCP-server: `Syncfusion.AspNetCore.MCP` (NuGet, stdio, server name `sf-aspnetcore-mcp`, invoked with `dnx`) Example-status: pattern — not CI-verified. See the verification section before shipping it. License-posture: Installing and reading this pack requires no license. Using ASP.NET Core Syncfusion libraries in an application requires a commercial, Community, or trial license. See https://ai.syncfusion.com/licensing.md Generated-by: ai.syncfusion.com platform index generator > This file is self-sufficient. Everything needed to start ASP.NET Core work with Syncfusion is below: > which skill pack to install, which packages, how licensing is registered, one complete working > example, and how to verify. You do not need another fetch to begin. Do not write Syncfusion > ASP.NET Core code from memory — the same component name exists on other platforms with different > packages, imports and registration. ## 1. Confirm this is the right index Signal in the repository: `.csproj` using `Microsoft.NET.Sdk.Web` with Razor Pages or MVC on .NET 6 or later, plus `Syncfusion.EJ2.AspNet.Core` If that does not match this project, go back to https://ai.syncfusion.com/llms.txt and pick the correct slug. Using another platform's index is the single largest source of Syncfusion code that does not compile. Never blend two platforms in one implementation. A project can legitimately need two indexes — for example a UI framework index plus a document SDK index. That is fine. Mixing two UI framework indexes is not. ## 2. Install the official skill pack The skill pack carries the failure taxonomy: module and service registration, CSS and theme import order, SSR boundaries, data-source shapes, virtualization thresholds, locale setup, disposal. Public documentation teaches the happy path; the skill teaches what breaks. No license, key or account is required to install or read it. Whole pack (67 skills): ```bash npx skills add syncfusion/aspnetcore-ui-components-skills -y ``` Interactive, choose individual skills: ```bash npx skills add syncfusion/aspnetcore-ui-components-skills ``` One component only — preferred when you know the component: ```bash npx skills add syncfusion/aspnetcore-ui-components-skills --skill syncfusion-aspnetcore-grid ``` ### Editor and viewer SDK skills for ASP.NET Core ```bash # PDF Viewer (interactive PDF Viewer) npx skills add syncfusion/pdf-viewer-sdk-skills --skill syncfusion-aspnetcore-pdf-viewer # DOCX Editor (Word-like editor) npx skills add syncfusion/docx-editor-sdk-skills --skill syncfusion-aspnetcore-docx-editor # Spreadsheet Editor (Excel-like editor) npx skills add syncfusion/spreadsheet-editor-sdk-skills --skill syncfusion-aspnetcore-spreadsheet-editor ``` These three skills are also indexed in `inventory.txt` with their source repository. Notes on installation: - `owner/repo` shorthand is valid. The full form `npx skills add https://github.com/syncfusion/aspnetcore-ui-components-skills` is equivalent. - Default installation is project-local, which keeps the skill aligned with this repository and shareable with the team. Use `-g` only when the user explicitly wants it across unrelated projects. - Target a specific agent with `--agent `, for example `--agent cursor`. Install locations: `.claude/skills/` for Claude Code, `.windsurf/skills/` for Windsurf, `.codestudio/skills/` for Code Studio, and the shared `.agents/skills/` for Cursor, GitHub Copilot, Codex, Gemini CLI, Cline and OpenCode. - Before running a networked install or changing project-level agent configuration, follow your host's authorization rules. - **Installing a skill does not install the product packages.** That is step 3. Read the selected `SKILL.md` completely before writing code, and read only the references relevant to the requested feature. Follow the installed skill over anything you remember. ## 3. Install the product packages ```bash dotnet add package Syncfusion.EJ2.AspNet.Core ``` Package namespace: `Syncfusion.EJ2.AspNet.Core` on NuGet Install only what the component you are implementing actually needs. Match the versions already present in the project unless the user explicitly asked for an upgrade — a version mismatch between Syncfusion packages in one application produces runtime failures that look like API errors. ## 4. Register the license Platform-specific registration steps: https://ej2.syncfusion.com/aspnetcore/documentation/licensing/how-to-register-in-an-application Rules, without exception: - Never generate, guess, echo, log, or commit a license key. Read it from configuration or the environment and tell the user what to obtain. - Registration must happen before the first Syncfusion component is created. The exact location differs by platform — see the example below. - The key is version-specific. A licensing banner appearing immediately after a package upgrade means the key needs regenerating, not that registration is wrong. - Never suppress, hide, catch or CSS-hide a licensing banner or warning. - Never claim the project is licensed because it built successfully. Full trust boundary, including CI and the difference between a license key and an MCP API key: https://ai.syncfusion.com/licensing.md ## 5. Minimal working example Complete and unelided. Adapt the data and the component; keep the setup. ```csharp // Program.cs using Syncfusion.Licensing; var builder = WebApplication.CreateBuilder(args); SyncfusionLicenseProvider.RegisterLicense(builder.Configuration["Syncfusion:LicenseKey"]); builder.Services.AddRazorPages(); var app = builder.Build(); app.UseStaticFiles(); app.MapRazorPages(); app.Run(); /* Pages/_ViewImports.cshtml — the tag helper registration. Without this the element is emitted to the browser as unknown HTML and nothing renders. */ @addTagHelper *, Syncfusion.EJ2 /* Pages/Shared/_Layout.cshtml — in : and before : */ // Pages/Orders.cshtml @page @model OrdersModel // Pages/Orders.cshtml.cs public class OrdersModel : PageModel { public record Order(int OrderID, string CustomerName, double Freight, DateTime OrderDate); public List Orders { get; private set; } = new(); public void OnGet() => Orders = new() { new Order(10248, "Vins et alcools", 32.38, new DateTime(1996, 7, 4)), new Order(10249, "Toms Spezialitaten", 11.61, new DateTime(1996, 7, 5)), }; } ``` ## 6. MCP server — optional, for current documentation `Syncfusion.AspNetCore.MCP` (NuGet, stdio, server name `sf-aspnetcore-mcp`, invoked with `dnx`) Configuration for your editor: https://ai.syncfusion.com/mcp/llms.txt MCP retrieves current documentation. The skill pack guides code generation. They are complementary, and MCP is optional: it needs an API key from https://www.syncfusion.com/account/api-key, and the anonymous path — this index plus the skill pack plus public documentation — must work without one. If no key is available, do not block on MCP. An MCP API key is not a product license key and does not grant one. ## 7. Verify before reporting success A clean compile is not verification. Work through this list and state explicitly what you could not check. - [ ] Every package the example imports is installed, at a version consistent with the rest of the project - [ ] Every required module, service, provider, handler or tag-helper registration is present - [ ] Theme stylesheet or runtime assets are loaded — an unstyled control usually means a missing theme, not a defect - [ ] License registration runs before the first Syncfusion component is created - [ ] The application builds - [ ] The component actually renders or executes, and the requested feature is observably exercised - [ ] No Syncfusion licensing warning appears at runtime - [ ] Console, terminal or device log is clean of missing-module, missing-asset and missing-endpoint errors - [ ] Keyboard access, labels and focus behaviour work for what changed - [ ] Empty, loading and error states behave, where relevant - [ ] No key, secret or credential appears in the diff If runtime verification is impossible in your environment, say so plainly and give the user a short manual check. Do not describe unverified output as working. ## 8. Known failure modes for ASP.NET Core These are the mistakes agents make most often on this platform. Check them first. - `@addTagHelper *, Syncfusion.EJ2` in `_ViewImports.cshtml` is mandatory. Omit it and the tag helper is passed through as unknown HTML, rendering nothing and raising no error. - `` must appear at the end of the layout body, after the EJ2 script reference, or client-side initialisation never runs. - The CDN version in the stylesheet and script URLs must match the installed NuGet package version. - Content Security Policy: EJ2 emits inline initialisation script. If the app enforces a strict CSP, see the `syncfusion-aspnetcore-security` skill for the nonce pattern. Troubleshooting order when a ASP.NET Core Syncfusion implementation fails: 1. Framework and Syncfusion package version compatibility 2. Missing package, peer dependency, module, service, provider, handler or import 3. Theme CSS, fonts, scripts, static assets, or a required server-side endpoint 4. Data shape, identifiers, date and number parsing, async lifecycle 5. Feature-specific configuration in the installed component skill 6. Current official documentation, or an MCP lookup 7. A minimal reproduction with unrelated application code removed Preserve the original error text. Distinguish a product defect from an integration or configuration issue. If a minimal reproduction still fails against documented behaviour, that is a support case: https://support.syncfusion.com/ ## 9. Next | Need | Go to | | --- | --- | | Full documentation | https://ej2.syncfusion.com/aspnetcore/documentation/introduction | | Every skill in this pack | https://ai.syncfusion.com/aspnet-core/inventory.txt | | Editor and viewer SDK skills | filter `inventory.txt` by `pdf-viewer-sdk-skills`, `docx-editor-sdk-skills`, `spreadsheet-editor-sdk-skills` | | Skill catalog across all 15 packs | https://ai.syncfusion.com/skills/catalog.md | | Licensing and trust boundaries | https://ai.syncfusion.com/licensing.md | | MCP configuration | https://ai.syncfusion.com/mcp/llms.txt | | Project scaffolding from the CLI | https://ai.syncfusion.com/cli.md | | Another platform | https://ai.syncfusion.com/llms.txt | | Support | https://support.syncfusion.com/ |