SyncfusionInc/Syncfusion.Licensingv24.2.8
✓ Verified
Syncfusion® licensing is a .NET library for validating the registered Syncfusion® license in an application at runtime. The Syncfusion® license must be registered in an application when using the Syncfusion® evaluation build or NuGet package assemblies. Documentation: https://help.syncfusion.com/common/essential-studio/licensing/license-key?utm_source=nuget&utm_medium=listing Support: Incident: https://www.syncfusion.com/support/directtrac/incidents/newincident?utm_source=nuget&utm_medium=listing Forum: https://www.syncfusion.com/forums/general?utm_source=nuget&utm_medium=listing This is a commercial product and requires a paid license for possession or use. Syncfusion’s licensed software, including this component, is subject to the terms and conditions of Syncfusion's EULA (https://www.syncfusion.com/eula/es/?utm_source=nuget&utm_medium=listing). To acquire a license, you can purchase one at https://www.syncfusion.com/sales/products?utm_source=nuget&utm_medium=listing or start a free 30-day trial here (https://www.syncfusion.com/account/manage-trials/start-trials?utm_source=nuget&utm_medium=listing). © Copyright 2026 Syncfusion®, Inc. All Rights Reserved. The Syncfusion® Essential Studio® license and copyright applies to this distribution.
Get Started
$ dotnet add package Syncfusion.LicensingReadme
Syncfusion licensing is a .NET library for validating the registered Syncfusion license in an application at runtime. The Syncfusion license must be registered in an application when using the Syncfusion evaluation build or NuGet package assemblies.
Code review template
| Title | Description |
|---|---|
| Task Link | |
| Solution description | |
| Areas affected and ensured | |
| Test cases | <br> Syncfusion-license repo testcase document.docx</br> |
| Testbed sample location | |
| Additional CheckList | <br>1. Did you run the automation against your fix? Yes</br><br>2. Is there any API name change?N/A</br><br>3. Is there any existing behavior change of other features due to this code change? No.</br><br>4. Does your new code introduce new warnings or binding errors? No.</br><br>5. Does your code pass all FxCop and StyleCop rules? N/A.</br><br>6. Did you record this case in the unit test or UI test? N/A |