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. Install the GrapeCity License Manager tool (gclm) in the pipeline.
   • If ActiveReports is already installed, then the gclm tool is already installed at 'C:\ProgramData\GrapeCity\gclm' location.
   • If ActiveReports is not installed, you may download the gclm deployment tool for:     
     • Windows:
        https://cdn.grapecity.com/license/gclm_deploy.exe
     • Linux/macOS:
        https://www.nuget.org/packages/GrapeCity.LicenseManagerTool/ or, you may install the gclm tool from command line:
       
       dotnet tool install -g GrapeCity.LicenseManagerTool

       
2. Before the build, activate the serial key. Run the following command in the command line:
   
   • Windows:
     

     gclm.exe "e88c1aa3-2781-44bb-b639-765c9ef6d15c" -a [serial key]
     
     

   • Linux/macOS:
     

     gclm "e88c1aa3-2781-44bb-b639-765c9ef6d15c" -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. After the build, deactivate the license activated in Step#2. Run the following command in the command line:
   
   • Windows:
     

     gclm.exe "e88c1aa3-2781-44bb-b639-765c9ef6d15c" -d [serial key]
     

   • Linux/macOS:
     

     gclm "e88c1aa3-2781-44bb-b639-765c9ef6d15c" -d
     

   Note:

   • The key should be deactivated even if the build is failed, otherwise the license cannot be activated for next build agent.
   • The environment should have the network to access sa2.grapecity.com website.

Pipeline script for licensing a project

Copy the following script in .yml file:

- task: VSBuild@1
  inputs:
    solution: '$(solution)'
    msbuildArgs: '/p:DeployOnBuild=true /p:WebPublishMethod=Package /p:PackageAsSingleFile=true /p:SkipInvalidConfigurations=true /p:DesktopBuildPackageLocation="$(build.artifactStagingDirectory)\WebApp.zip" /p:DeployIisAppPath="Default Web Site"'
    platform: '$(buildPlatform)'
    configuration: '$(buildConfiguration)'
 
- task: CmdLine@2
  inputs:
    script: 'C:\ProgramData\GrapeCity\gclm\gclm.exe e88c1aa3-2781-44bb-b639-765c9ef6d15c -a <license key>'
 
- task: VSBuild@1
  inputs:
    solution: '$(solution)'
    msbuildArgs: '/p:DeployOnBuild=true /p:WebPublishMethod=Package /p:PackageAsSingleFile=true /p:SkipInvalidConfigurations=true /p:DesktopBuildPackageLocation="$(build.artifactStagingDirectory)\WebApp.zip" /p:DeployIisAppPath="Default Web Site"'
    platform: '$(buildPlatform)'
    configuration: '$(buildConfiguration)'
 
- task: CmdLine@2
  inputs:
    script: |
      C:\ProgramData\GrapeCity\gclm\gclm.exe e88c1aa3-2781-44bb-b639-765c9ef6d15c -d <license key>