Runtime License File Clarifications

Runtime License File Clarifications

Posted by: enrique.pv-ext on 15 April 2026, 7:40 am EST

• 

  enrique.pv-ext

  • Post Options:
  • Link
    Copy

  Posted 15 April 2026, 7:40 am EST

  Runtime License File Clarifications

  The documentation states that the runtime license file (.gclicx / .sa3licx) is generated per application and must be embedded as a resource.

  Can you confirm whether the content of the file is tied only to the application name, or also to:

  The machine where it was generated?
  
  The developer license used to generate it?

  What happens if the embedded runtime license file is:

  Missing from the build?
  
  Accidentally removed or replaced with a license generated for another app?

  Developer License vs Runtime License Behavior

  If a developer does not have an active ComponentOne license:

  Can the solution be opened and compiled if no ComponentOne controls are modified?
  
  Is compilation fully blocked, or is it blocked only when controls are referenced?

  In this scenario, which of the following is the expected behavior?

  Compilation error
  
  Runtime license file not generated
  
  Warnings only
  
  License validation failure at runtime

  Please clearly specify what is allowed and what is not allowed for unlicensed developers working on an existing project.

  CI/CD and Build Pipelines

  For automated build environments:

  Is the GCLM pipeline/build license mandatory for CI/CD?
  
  Can a runtime license be generated only once and reused in pipelines, or must it be regenerated as part of the build?

  Could you please provide:

  Supported CI/CD scenarios
  
  Licensing requirements
  
  Pricing information for pipeline licenses

  License Management & Deployment

  In the My Account / Licensing portal:

  Is it possible to view the specific machine names that are currently activated?
  
  Can an activation be remotely deactivated without having access to the physical machine?

  For production deployment:

  What is the exact technical list of files required to avoid license issues?

  licenses.licx
  
  .gclicx / .sa3licx
  
  Any specific DLLs or runtime components

• 

  kartik.dua

  

  • Post Options:
  • Link
    Copy

  Posted 16 April 2026, 3:31 am EST

  Hi,

  Here’s a brief overview of C1 licensing:

  To successfully license a project that uses C1 controls, you must first activate a valid license key on the machine.

  Once the license is activated, your project must include a valid embedded license file to run without any licensing errors. Since your project is an ASP.NET WebForms application based on .NET Framework, it can be licensed using either a licenses.licx file (design-time license) or a .gclicx file (runtime license).

  If the machine does not have an activated license, the project will not embed a valid license file, and licensing errors will occur. Therefore, activating the license on the machine is a required step.

  ---

  Just for your information, the .sa3licx file is not relevant in your scenario. The ASP.NET WebForms is an older platform and it is already in maintenance mode. So, even in the latest 2025v2 version, it still uses the older GCLM-based licensing rather than the newer SA3 licensing model we introduced just now.

  ---

  Regarding pipeline licensing:

  CI/CD pipeline implementations typically involve multiple builds within a single day. Additionally, most modern CI/CD platforms use virtual runners, that are temporary VMs that are created for a build and then discarded afterward.

  Standard developer licenses have certain limitations. For example, they can only be activated on up to three machines at a time, and there are restrictions on the number of activation-deactivation cycles per day. These limitations can affect CI/CD pipeline scenarios.

  To address this, we offer a separate pipeline license that allows an unlimited number of activations and does not impose limits on activation-deactivation cycles. This enables users to perform multiple simultaneous builds as many times as needed throughout the day.

  ---

  For any details related to pricing or purchase, please directly contact the sales team.

  Best Regards,
  
  Kartik

• 

  enrique.pv-ext

  • Post Options:
  • Link
    Copy

  Posted 16 April 2026, 4:52 am EST

  Follow-up Questions Regarding Pipeline Licensing (Pricing & CI/CD Usage)

  Thank you for the explanation regarding the need for a dedicated pipeline license in CI/CD scenarios.
  
  To properly evaluate and plan this, we would appreciate clarification on the following points:

  1. Pricing and Commercial Model

  Could you please provide pricing information for the ComponentOne Pipeline License?

  What is the commercial model of the pipeline license? Is it licensed per:

  Organization / company
  
  Project
  
  Product
  
  CI/CD agent / build server
  
  Other (please specify)

  Is the pipeline license:

  Subscription-based or perpetual?
  
  Aligned with ComponentOne versioning (annual renewal vs major versions)?

  2. Scope of Use in CI/CD Environments

  Does a single pipeline license cover:

  Multiple pipelines?
  
  Multiple build agents/runners?
  
  Multiple applications/products built within the same organization?

  Are there any technical or contractual limitations regarding:

  Concurrent builds
  
  Parallel pipelines
  
  Number of projects using the same pipeline license?

  3. License Activation and Key Management in CI/CD

  How is the pipeline license activated in a CI/CD environment?

  Is a license key / serial provided specifically for pipeline usage?
  
  Is activation performed via GCLM on the build agent/runner?

  How should licensing be handled in ephemeral agents (temporary VMs or containers created per build)?

  4. Offline / Restricted Network Scenarios

  How can a pipeline license be used in a CI/CD agent without internet access?

  Is offline activation supported?
  
  Is there a documented process to:

  Generate an offline request file
  
  Activate the license on another machine
  
  Import it into the CI/CD agent?

  Is there an official guide or documentation describing:

  Pipeline license activation
  
  CI/CD integration
  
  Offline or restricted-network scenarios?

  5. Runtime License Generation (.gclicx)

  In a CI/CD setup:

  Is the .gclicx runtime license expected to be generated during the pipeline?
  
  Or can it be generated once and reused across builds?

  Are there any rules or best practices regarding:

  Reusing the same .gclicx file across pipelines or environments
  
  Regenerating it per build or per application version

  Thank you in advance for clarifying these points. This information is required for us to define a compliant and scalable licensing strategy for our CI/CD infrastructure.

• 

  kartik.dua

  

  • Post Options:
  • Link
    Copy

  Posted 16 April 2026, 9:31 am EST

  Hi,

  1. All queries related to pricing, purchases, and subscriptions are handled by the sales team, not the support team. We kindly request that you contact them directly for such inquiries.

  2. The pipeline-related questions you raised are covered in our documentation on Pipeline Licensing - https://developer.mescius.com/componentone/docs/license/online-license/common-licensing-scenarios/licensing-apps-on-docker-with-pipeline

  3. To license your projects, you can embed either a licenses.licx file or a .gclicx file in your project. During the build process (on the pipeline machine), the pipeline license should be activated on that machine, allowing the build to succeed without any issues. So, it is not necessary to generate a runtime license (.gclicx file) on the pipeline machine itself.

  Best Regards,
  
  Kartik