The GrapeCity License Manager (gclm) tool identifies the machine via the host-name. However, in pipeline environments, the build actions work in virtual machines or dockers on cloud, so the host-name would be different in each build process. The environments may also be reset before every build so that the activated license is removed.

The steps to license the applications with pipelines are as follows:

1. Deploy the application. If the gclm tool is not already installed, it will be installed by NuGet packages if the pipeline has access to it. The gclm tool is also available on CDN here: https://cdn.grapecity.com/license/gclm_deploy.exe
   Note that the project is built with Trial License for 30 days.
   
2. Activate the serial key. Run the following command in the command line:
   

   gclm.exe "de456e2c-d2e3-4246-94e8-9648bbd6fbf0" -a [serial key]
   

3. Rebuild the application with the activated license. This step is required since the gclm tool is run and the license is validated.
4. Run the deployed application using dotnet command. For example:
   

   dotnet JSViewerApplication.dll
   

5. Deactivate the license activated in Step#2. Run the following command in the command line:
   

   gclm.exe "de456e2c-d2e3-4246-94e8-9648bbd6fbf0" -d [serial key]
   

   
   The license should be activated.