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:
dotnet tool install -g GrapeCity.LicenseManagerTool
gclm.exe "e88c1aa3-2781-44bb-b639-765c9ef6d15c" -a [serial key]
gclm "e88c1aa3-2781-44bb-b639-765c9ef6d15c" -a [serial key]
dotnet JSViewerApplication.dll
gclm.exe "e88c1aa3-2781-44bb-b639-765c9ef6d15c" -d [serial key]
gclm "e88c1aa3-2781-44bb-b639-765c9ef6d15c" -d
Note:
Copy the following script in .yml file:
Example Title |
Copy Code
|
---|---|
- 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> |