MESCIUS licensing is based upon the development machine. However, in a pipeline environment, the license needs to be activated on a virtual machine or docker on the cloud. If your pipeline has a dynamic agent (for example, Azure pipeline with Microsoft-hosted agents) you must activate the license before each build and deactivate the license after each build and, depending on the type of license, you may need to deactivate the license after each build. See the instructions below for your type of license.

Activation with Standard Developer License

With a standard developer license you may build and deploy applications from a dynamic build agent with some limitations.

1. Your serial key must be activated and deactivated for each build.
2. You may only activate and deactivate a single key up to 9 times per day.

To activate your serial key on the build server follow these steps:

1. Install the MESCIUS License Manager tool (gclm) in the pipeline.
   1. If any MESCIUS product is installed, then the gclm tool is already installed at (C:\ProgramData\GrapeCity\gclm)
   2. If no  MESCIUS product is installed, you may download the gclm deployment tool:
      1. Windows: https://cdn.grapecity.com/license/gclm_deploy.exe
      2. 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, call the gclm tool to activate the license
   1. Windows: C:\ProgramData\GrapeCity\gclm\gclm.exe "product id" -a "key"
   2. Linux/MacOS: gclm "product-id" -a "key"
3. After the build, call the gclm tool to deactivate the license
   1. Windows: C:\ProgramData\GrapeCity\gclm\gclm.exe "product id" -d
   2. Linux/MacOS: gclm "product id" -d

For a complete list of product ids, see Activation by Command Line.

Notes:

• The key should be deactivated even if the build is failed, otherwise the license cannot be activated for next build agent. You may contact our support team to resolve the issue if a key cannot be deactivated. If deactivation may be a problem, we recommend upgrading to a pipeline license.
• The environment should have the network to access sa2.mescius.com website.
• By default, there is a limit of nine (9) activations/deactivations per 24 hour period. This is known as reactivation.

Activation with Pipeline License

With a ComponentOne pipeline license you may build and deploy applications from a dynamic build agent with fewer limitations than a standard developer license. A pipeline license allows unlimited activations per day with no need to deactivate the key. The serial key must still be activated before each build, but it does not require network access and it cannot be used for design-time development.

A pipeline license can be obtained by contacting sales. A pipeline license includes three things:

1. Serial Key
2. Local Activation Package File
3. Password

To activate your pipeline serial key on the build server follow these steps:

1. Install the MESCIUS License Manager tool (gclm) in the pipeline.
   1. If the ComponentOne product (for example, ASP.NET Core MVC Edition) is installed, then the gclm tool is already installed at (C:\ProgramData\GrapeCity\gclm)
   2. If no ComponentOne product is installed, you may download the gclm deployment tool:
      1. Windows: https://cdn.grapecity.com/license/gclm_deploy.exe
      2. 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. Copy the Local Activation Package file to the gclm install location.
   1. Windows: C:\ProgramData\GrapeCity\gclm
   2. Linux/MacOS: ~/.local/share/GrapeCity/gclm
3. Before the build, call the gclm tool to activate the license using your serial key and provided password.
   1. Windows: C:\ProgramData\GrapeCity\gclm\gclm.exe "331cf6cd-b73c-429f-ba79-fa2f85eebd68" -a "key" “password”
   2. Linux/MacOS: gclm "331cf6cd-b73c-429f-ba79-fa2f85eebd68" -a "key" “password”

Notes:

• You may also perform the activation (step 3) using the MESCIUS License Manager GUI if command line interface is not required. See Activating a Serial Key and follow the steps activating your pipeline key for ComponentOne Studio Enterprise. It will prompt you to enter the password separately.
• With a pipeline license the product-id is always 331cf6cd-b73c-429f-ba79-fa2f85eebd68 (Studio Enterprise)