Skip to content
P4 Software P4 Software / BarcoderX English

Add these docs to Claude

Ask Claude questions about these docs. Claude reads the published pages and links you back to them. Copy this address:

https://p4-software.opendocs.page/mcp

In claude.ai or Claude Desktop: open Settings, then Connectors, choose Add custom connector and paste the address.

In Claude Code, run:

claude mcp add --transport http docs https://p4-software.opendocs.page/mcp

Evaluation mark and license keys

Evaluation mark and license keys

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.

Using BarcoderX without a key

BarcoderX is fully usable without a license key. The only difference is the evaluation mark.

  • The mark is a set of black badges laid across the whole label. Each carries the white words 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.
  • The badges are sized from the label's size, so the mark is the same on every printer and every platform, and it has at most 228 badges however long or narrow the label is. It sits above every other element, and it shows on a black label as well as on a white one.
  • Barcodes stay scannable where there is room. A badge is left out where it would touch the bars of a barcode, its quiet zones or a small margin around them, so a scanner reads the symbol as it would without the mark. This keeps clear only barcodes with dark bars that nothing drawn after them touches and that are big enough to scan in practice, with modules at least 0.15 mm wide and bars at least 2 mm tall. The printed digits under a barcode are not kept clear, so a badge may cover them. The label is cut into eight equal bands across and eight down, and every band always carries at least one badge. Badges with words always cover at least a quarter of the bands. Badges go where there is free room, away from barcodes, and they may lie over text and other graphics: the mark protects scanning, not reading. Only where a label leaves no free room is a badge drawn over a barcode, at the place where it hides the least, and then it can cover part of a barcode or its quiet zone. A quiet zone is kept clear only up to 11 modules on each side, and a barcode whose bars are off the label is not kept clear at all. The mark is a deterrent on pictures, not a lock.
  • A mark that cannot be made in full is made in a simpler form, and never left out. If the check of the license itself fails, the result is the same: the label is marked, and the message BX9030 says so. The label is still printed.
  • Every label of a job carries it, including each label on a roll or sheet with several labels across.
  • It appears in every output: images, PDF, SVG, HTML and EPS, and in the printer commands. For printers, it is sent as a graphic and is the last thing drawn on the label. Because it is not a printer command, a new printer language needs nothing extra to show it.
  • The label editor does not mark its previews of single elements. When its add-on is not licensed, it shows its own banner and a watermark instead.

Evaluation keys

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.

License states

StateOutputWhat you see
LicensedNo markNothing
EvaluationNo markAn information message with the days remaining
GraceNo markA warning with the reason and the date marking will start
UnlicensedMarkedA 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.

Never stops printing

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.

Registering a key

You can register a license key in four ways. BarcoderX uses the first way that provides a key:

  1. A call in your code, at start-up.
  2. Your application's configuration, including the dependency injection options.
  3. Environment variables.
  4. A file named 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.

Verified on your machine

  • A license key is a signed document. BarcoderX verifies the signature on your own machine, with the cryptography that comes with .NET. It needs no network.
  • Signature verification happens once for each license in a process, so it does not slow down your labels.
  • BarcoderX tolerates a clock that is a day or two out. If it detects that the clock was set back, it reports it and prints anyway.
  • A signed list of revoked licenses ships with each release and can be refreshed online. A revoked license takes effect from a date that is set in the list.

Activation

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.

  • An activation or check-in sends only the license ID, a hashed fingerprint of the machine, and the version of BarcoderX. It sends no machine name, user name, application name or usage data. The fingerprint mixes in the license ID, so it cannot be matched across licenses.
  • It never blocks output. If the network is closed or the check fails, printing and rendering go on exactly as before. The worst case is still marked output.
  • Sites without internet can activate by exchanging two files: you create a request file and send it to BarcoderX, and you install the response file that comes back.
  • A developer license covers one named developer on up to three machines. Moving an activation to another machine is done from the developer's account. This guide describes it when the account page is available.
  • Build servers are covered by your team's developer licenses. Running your finished application in production needs a deployment license, and an OEM license covers redistribution.
  • A 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.

Checking the release stamp

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 codeWhat it meansWhat to do
0The stamp is valid.Nothing.
10The file has no stamp, so it is not a released build of BarcoderX.Use the BarcoderX.Licensing.dll file from an official release package.
11The 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.
12The 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.
2The 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.
3An 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?