P4 Software
/
BarcoderX English
Applies to: BarcoderX Basic and Ultimate
Status: Planned. Nothing is released yet and there is nothing to download. This page describes how licensing is designed to behave. Time values such as the length of an evaluation and of a grace period are set before the first release, so this page does not state them.
BarcoderX is fully usable without a license key. The only difference is the evaluation mark.
BARCODERX EVALUATION, or, where room is short, only the word BARCODERX or a white stripe. The words exist in Spanish too (BARCODERX EVALUACIÓN). Until a job carries a language of its own, the English words are used.A time-limited evaluation key removes the mark until it expires, and tells you how many days remain. After it expires, output is marked again, with no grace period. You can register a new evaluation key at any time.
| State | Output | What you see |
|---|---|---|
| Licensed | No mark | Nothing |
| Evaluation | No mark | An information message with the days remaining |
| Grace | No mark | A warning with the reason and the date marking will start |
| Unlicensed | Marked | A warning with the reason |
Grace is a short period during which a license that has lapsed still gives unmarked output. A key that is forged, malformed or compromised gets no grace.
A perpetual license is valid for any release dated on or before the end of its updates window. A release that is dated after your updates window ends is marked from its first run, so you see it in development and test and never find out in production.
If you use a feature that your license does not cover, for example a symbology that your edition does not include, the job still completes. Its labels are marked, and a message names what is missing.
No license problem ever throws an error from, blocks, delays or fails a render, an export, a command generation or a print. Whatever goes wrong inside licensing, such as a missing key, a damaged key, a missing or locked license file, a clock set wrongly or an unreachable activation service, the result is marked output at worst. The printer still receives a complete, valid label. This is tested for every fault in a list that includes all of those.
Licensing does no input or output while a job runs, so a license check cannot make a job wait.
You can register a license key in four ways. BarcoderX uses the first way that provides a key:
barcoderx.lic next to your application.One source can hold several keys, for example an SDK key and an editor add-on key. BarcoderX combines them. A bad key never causes an error. It is recorded as a diagnostic and the affected product runs unlicensed. Your key is a secret, so BarcoderX never writes it to a log. Logs carry only the license ID.
A host, such as the web API, checks the license at start-up and never refuses to start because of it. It shows the state, without the key, at GET /api/v1/meta/licence.
As decided, a license is activated online when you register it, and BarcoderX checks in from time to time. How often, and what happens when a license is used on too many machines, are not decided yet. The terms of the license will state this openly.
bx-license tool ships with the SDK. It shows the license state, verifies a file, and handles activation and revocation refresh, in English or Spanish. It never prints the key. It also checks a release stamp: see the next section.The data that licensing sends and stores will be documented in the product documentation and in a privacy notice.
Each release is meant to carry a signed release stamp: the date of the build and the name of the release, signed by P4. The command bx-license stamp verify --assembly <file> checks the stamp inside a BarcoderX.Licensing.dll file. It checks that P4 signed the build date and the release name, and that the release name matches the version of the file. It does not check the rest of the file. It only reads the file: it changes nothing and sends nothing. Messages are in English or Spanish.
When the stamp is valid, the command shows the key id, the build date and the release name, and the exit code is 0. In every other case it shows one message that says what to do. The exit code says which case it is:
| Exit code | What it means | What to do |
|---|---|---|
| 0 | The stamp is valid. | Nothing. |
| 10 | The file has no stamp, so it is not a released build of BarcoderX. | Use the BarcoderX.Licensing.dll file from an official release package. |
| 11 | The stamp is not valid for this file. It may be damaged, signed with a key that the tool does not trust, or made for a different release from the version of the file. | Install the file again from an official release package. |
| 12 | The stamp is dated later than today (UTC). | Check the date of this computer. If it is right, the stamp is wrong: write to support@barcoderx.com and give the message. |
| 2 | The command was used wrongly, or the file was not found, cannot be read, is too large or is not a .NET assembly. | Check the path and your access to the file, make sure that you named the BarcoderX.Licensing.dll file, and run the command again. |
| 3 | An unexpected problem stopped the check. Nothing was changed. | Run the command again. If it happens again, write to support@barcoderx.com, give the message and say how to reproduce the problem. |
The messages also say what to do for whoever builds BarcoderX releases: use the stamp that the release process signed for that exact build. Until a release is stamped, a build has no stamp and the command answers 10.
BarcoderX is a product of P4 Software.
Was this page helpful?