Concise guidance for license generation, registration, and best practices for ASP.NET MVC applications. Detailed troubleshooting steps, secure storage patterns, and code examples live in references.
When to Use
- Registering or updating Syncfusion license keys for ASP.NET MVC EJ2
- Troubleshooting license validation, version, or platform mismatches
- Configuring license registration for build servers and CI/CD pipelines
- Securing license keys in production environments
- Upgrading from trial to production licenses
Key Points for ASP.NET MVC
License Registration Location
- File:
Global.asax.csorGlobal.asax.vb - Method:
Application_Start() - Timing: Must execute BEFORE any Syncfusion control initialization
Platform-Specific Requirements
- Package: License key must match
Syncfusion.EJ2.MVC5version - Licensing NuGet: Ensure
Syncfusion.LicensingNuGet is installed and matches Syncfusion package version - No Web.config: License is NOT stored in Web.config; register programmatically only
Quick Checklist
✓ Generate license key for correct Syncfusion version and ASP.NET MVC platform
✓ Register key in Global.asax Application_Start() method BEFORE control use
✓ Ensure Syncfusion.Licensing NuGet package version matches Syncfusion EJ2 version
✓ Store keys securely: Use environment variables, Azure Key Vault, or encrypted config
✓ Never commit license keys to source control
✓ Test license registration early in development
✓ Have fallback license strategy for build/CI environments
Security Best Practices
- Use environment variables:
Environment.GetEnvironmentVariable("SYNCFUSION_LICENSE") - For Azure: Store in Azure Key Vault and retrieve via managed identity
- For on-premises: Use encrypted configuration sections or secure vaults
- Rotate licenses before expiration; implement monitoring
- Document license scope (developer, production, trial) per environment
References
- License generation & claiming: references/syncfusion-license-guide.md
- Registration & troubleshooting: references/syncfusion-license-registration.md