1. Home
  2. Forum
  3. Blazor
  4. Store and use Syncfusion License Key in Blazor WebAssembly

Store and use Syncfusion License Key in Blazor WebAssembly

What is the recommended way to store and access the Syncfusion License Key in a Blazor WebAssembly Project?
I've looked at a few posts about storing license keys in Blazor WebAssembly Apps in general, but there don't seem to be any solid answers at this stage.

5 Replies 1 reply marked as answer
JA Jesus Arockia Sankaran S Syncfusion Team July 16, 2020 01:09 PM UTC

Hi Adriaan, 

Thank you for contacting Syncfusion support.  

We would like to let you know that we currently don’t have an option to hide the license keys which is registered in the project since everything is shipped to Browser in Blazor WebAssembly and we do not have control over the hardware. We have implemented this licensing (key) validation system to avoid using our products inadvertently. Instead if you are a licensed customer you can use the licensed installer, there is no need to register the license key in your application.  

Please refer the following link and download the latest v18.2.0.44 web installer or offline installer for your requirement from your account.  

 
Refer the following documentation link for the step by step installation of Syncfusion Installer.  

 
 
If you are using the trial installer or NuGet packages from nuget.org, then you should generate and register the corresponding version and platform license key in your application 

Let us know if you need further assistance. 

Regards, 
Jesus Arockia Sankaran S 


ZY Zhi Yuan August 22, 2020 04:22 AM UTC

Hello,

One of the reasons for using Blazor Wasm rather than Blazor Server is because "an ASP.NET Core web server isn't required to host the app. Serverless deployment scenarios are possible (for example, serving the app from a CDN)." (https://docs.microsoft.com/en-us/aspnet/core/blazor/hosting-models?view=aspnetcore-3.1#blazor-webassembly) I'm planning to do that, since it significantly reduces the cost compared to having it hosted on a ASP.NET CORE web server.

A serverless deployment means that I'm not given access to the machine, so I don't think I'm able to use the installer and install Syncfusion on the machine.

Therefore, how should I go about resolving this issue?

Thank you!

Regards,
Zhi Yuan

Edit: I went to see how Telerik solves this problem, and it seems that they offer some sort of ZIP Archive method (https://docs.telerik.com/blazor-ui/getting-started/what-you-need#telerik-specific-packages) to get the nuget packages, without having to specify the license key in the source code.

JA Jesus Arockia Sankaran S Syncfusion Team August 24, 2020 12:49 PM UTC

Hi Zhi Yuan, 

Thanks for your update. 

As we stated in our previous update, there is no need to configure the License key to the Blazor WASM application source when you have installed the Syncfusion license build and used the NuGet packages from the installed location (local NuGet feed).  

The license key configuration only required when you have installed the NuGet packages from trial build or directly from the nuget.org.  

Telerik shared the licensed NuGet packages as Zip format whereas we provide it as build installer for evaluating our samples in the local machine. 

Please let us know if you need any further assistance on this. 
 
Regards, 
Jesus Arockia Sankaran S 


Marked as answer
FR Frederiek February 14, 2023 01:45 PM UTC

And how exactly are we supposed to build this then in a CI pipeline (like github actions for instance)?


BH BharatRam Harikrishnan Syncfusion Team February 17, 2023 10:45 AM UTC

Hi Frederiek,


To build your project with Syncfusion licensed NuGet packages in a CI pipeline like GitHub Actions, you need to ship our licensed packages to any repository manager like Nexus, Azure DevOps feed, etc. Then, in your GitHub Actions workflow, you can restore the packages from your private package source located at the repository manager by using the following YAML code:


.yaml

jobs:

build:

runs-on: ubuntu latest

 

Steps:

//…

- name: Restore packages

run: dotnet restore --source "https://myprivatenupkg.com"

- name: Build

run: dotnet build MyProject.csproj

//…


By following this procedure, you will be able to use Syncfusion licensed NuGet packages to build your project in CI pipeline. For further reference, please see the links below:

https://learn.microsoft.com/en-us/dotnet/core/tools/dotnet-restore#options

https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-net#using-the-net-starter-workflow


Regards,

Bharat Ram H


Loader.
Up arrow icon