Licensing Syncfusion

[Ignacio Amezcua]

Hi Syncfusion Team,

I have been working with my team to secure as much of our application as possible and in that, we want to be able to remove the app key that we normally use to license the use of Syncfusion in our application so it is not exposed to the world. I have read through your documentation and have followed the steps to downloading and installing Syncfusion Studio and Licensing the latest version of the Blazor Nuget Packages so I wouldn't have to include the App Key in my code. This is the guide I am referring to:  Install the Syncfusion Blazor offline installer | Syncfusion

Here is a screenshot of the Studio showing that my Blazor installation is licensed:

Here is a link to where I am downloading the studio from:  Essential Studio® Enterprise Edition Downloads | Syncfusion®

After installation, I reference the Nuget packages that are built in my C:\Program Files(x86)\Syncfusion\Essential Studio\Blazor\32.2.3\NuGetPackages folder and after running the front end of my application and removing references to the key, I get the following message:



I have tried uninstalling and reinstalling, using the login feature to license the packages, using an unlock key to reference the packages, using the web installer, using the offline installer but they all amount to the same result.

I was under the impression that if the nuget packages were built using the licensed version of the studio, I would not have to include the app key.

How can I resolve this issue? I do not want to use the app key in my code since it would be exposed for anyone to access.

Thank you,

Ignacio Amezcua

[Prashanth Sundhar]

Hi Ignacio,
 

Please ensure that all Syncfusion packages referenced in your project are loaded from Syncfusion Essential Studio Blazor installation directory.

C:\Program Files(x86)\Syncfusion\Essential Studio\Blazor\32.2.3\NuGetPackages

Referencing assemblies from nuget.org /trial installer or previously copied DLLs, outdated package folders, or mixed sources—may result in licensing validation issues, including the appearance of a trial license popup during application execution.

Additionally, verify that every Syncfusion assembly in your project’s output folder is built without the “LR” (License Required) suffix. The presence of even one assembly with the “LR” designation is sufficient to trigger the trial license warning at runtime.
 

Without LR	With LR

To avoid this, carefully inspect your output directory and ensure that all Syncfusion DLLs are consistent, properly licensed, and sourced exclusively from the Syncfusion installation path.
 

If you find that all Syncfusion assemblies in the output folder are marked with the “LR” suffix, clear NuGet cache, delete the entire output, bin,obj directory and perform a clean rebuild of the solution

If the reported issue is still not resolved, please share us the following details to check issue further from our side,

1. A complete list of the Syncfusion libraries currently referenced in your project, including:
   
   

·        The assembly names

·        The version numbers

·        The file paths from which they are being referenced

Please let us know if you have any concerns.

Regards,

Prashanth S.