BarcodingBarcode and RFID components

Barcode and RFID components

Identification, built into your code.

Components for developers: generate barcodes in applications, reports and services. Choose the right family for .NET, ActiveX, Delphi, PHP or Java.

Software · Equipment · Implementation

ROSISTEMDEVELOPER COMPONENTS

FROM YOUR APPLICATION DATA

.NETActiveXDelphiPHPJava
DataComponentDocument
ROSISTEM / BARCODINGFrom your application
to the physical world.
Codes · Labels · Reports
BUILT FOR WORKApplications and servicesReports and documentsLabels and identification

WHY Barcoding

Generate identifiers where your data already lives.

Integrate codes into your application documents and workflows. Compatibility is checked against your technology, version and required output format.

AT A GLANCE

Barcoding in figures

Developer components that generate barcodes and encode RFID directly from your application, plus a REST API with a typed .NET client.

.NET · ActiveX · Java · PHP · VCL
Component families for barcode generation
82
Symbologies supported by the ActiveX component
9
TrueType barcode fonts for reporting tools
ZPL II · DPL
Printer languages in the RFID encoder, plus a custom command
netstandard2.0 · net8.0
Target frameworks of the .NET SDK for the REST API (.NET Framework 4.7.2+ and .NET 6+)
since 2003
Barcode and RFID technology developed by Rosistem

ABOUT THE SOLUTION

Identification is built into the application, not added at the end.

When a report, label or document needs a scannable code, the application that owns the data remains the source of truth. The Barcoding family supports integrating identifier generation into software projects. Component selection starts with the runtime environment, technology and the place where the output needs to appear.

The .NET, ActiveX, Delphi/VCL, PHP and Java families address different technical contexts. Evaluation considers the project version and architecture, required symbology and output format. For RFID integration, the trial also includes the reader, tag and the material carrying it. The technical decision can then rely on a result checked in the actual application.

SOLUTION ARCHITECTURE

Where the components sit in your application

The component runs inside the application that owns the data. The code is generated where it is used: in a form, web page, report, label or RFID tag.

Where the components sit in your application Barcoding components.NET, ActiveX, Java, PHP and VCLlibraries that draw the code as animage, not a font Developer applicationWinForms, WPF, ASP.NET, Delphi, Javaor PHP — the component is part of theprojectData sourceBarcode value bound to the fields ofa data set (data binding)Reports and documentsCodes in Crystal Reports, ReportingServices and Office documentsPrintersAny printer installed in Windows;cheque printers with MICR supportRFID encodersEPC data written to the tag when thelabel prints, from the applicationRosistem WMS REST APIOpenAPI specification and a typed C#client generated from itWatched PDF folderPDF Directory Printing prints everynew PDF automatically
  • Developer application WinForms, WPF, ASP.NET, Delphi, Java or PHP — the component is part of the project
  • Data source Barcode value bound to the fields of a data set (data binding)
  • Reports and documents Codes in Crystal Reports, Reporting Services and Office documents
  • Printers Any printer installed in Windows; cheque printers with MICR support
  • RFID encoders EPC data written to the tag when the label prints, from the application
  • Rosistem WMS REST API OpenAPI specification and a typed C# client generated from it
  • Watched PDF folder PDF Directory Printing prints every new PDF automatically

THE WORKFLOW

From choosing a component to a code read on real equipment

Integration starts with choosing the component and ends with validation on real equipment; support and updates continue after delivery.

Step
01Component selection
02Installation in the project
03Configuration and data binding
04Generation in the application workflow
05Validation on equipment
06Support and updates
Team
Software architect
Developer
Developer
Developer
Testing team
Rosistem
Application
.NET, ActiveX, Java, PHP or VCL family
Visual Studio, Delphi / C++ Builder, Java IDE, PHP
Properties panel / Object Inspector
Form, web page, report or image file
Printer, reader, RFID encoder
Technical support by e-mail
Result
Platform, runtime version, symbologies, output format
Component package and licence key
Symbology, data to encode, resolution, quiet zone, text
Raster or vector image at the required resolution
Sample labels and documents, read results
Component updates and technical answers

01 / .NET

Components for .NET applications.

Integration into .NET applications and services to generate identifiers and include them in documents.

Explore capabilities ↗
Barcodes in reportsView details ↗

02 / ActiveX

Integration in existing Windows applications.

Components for Windows applications using COM/ActiveX interfaces.

Explore capabilities ↗
Data bindingView details ↗

MODULES AND CAPABILITIES

Twelve components and utilities

01

Rosistem Barcode .NET

Control for WinForms and WPF applications, added from the Visual Studio toolbox.

  • Linear: Code 128, Code 39, Code 93, EAN-13, EAN-8, UPC-A, UPC-E, ISBN
  • 2D: Data Matrix, QR Code, PDF417, MicroPDF417, Aztec
  • Configurable DPI resolution, rotation, quiet zone and human-readable text
  • Check digits calculated by the component
  • Data binding through bindingSource / dataSet
  • Samples included: WinForms C#, VB.NET console
02

Rosistem Barcode ASP.NET

Server-side barcode generation in ASP.NET web application pages.

  • Image generated on request in the page
  • Same symbologies as the .NET component
  • Sample web application project included
03

Barcodes in reports

Barcodes in reports generated by the application, bound to the report data.

  • Crystal Reports: C# sample included
  • Component for Reporting Services / RDLC
  • 2D codes (e.g. PDF417) on every report record
04

Rosistem Barcode ActiveX

ActiveX control for compatible hosts: Visual Basic, Access, Word, Excel, PowerPoint.

  • 82 symbologies
  • GS1-128, GS1 DataBar, Composite, HIBC
  • Postal: Royal Mail, Australia Post, USPS OneCode, KIX
  • Property dialog: data, symbology, height, colours
  • Embedded as an object in Excel sheets
05

Rosistem Barcode VCL

VCL components for Delphi and C++ Builder, configured from the Object Inspector.

  • Builds for Delphi 6, Delphi 7, XE7 and RAD Studio 10.2
  • GS1: FNC1 for Code 128 / GS1-128 and composite formats
  • Data Matrix: ASCII, Binary, C40, Text, X12, EDIFACT encodation; ECI
  • QR Code: ECC level L, M, Q, H and Micro QR
  • PDF417: Standard, Micro, Truncated, Macro; 8 security levels
  • Rotation by 90, 180 and 270 degrees
06

Rosistem Barcode Java

Java classes for 1D and 2D barcode generation, including server-side through a servlet.

  • Separate packages for 1D and 2D codes
  • Servlet for server-side image generation
  • Image encoding included in the library
07

Rosistem Barcode PHP

PHP class library that renders barcode images from scripts, with no native dependencies.

  • Codabar, Code 11, Code 39, Code 93, Code 128
  • EAN-8, EAN-13, UPC-A, UPC-E, ISBN
  • Interleaved 2 of 5, Standard 2 of 5, MSI, POSTNET
  • Suited to invoices, order confirmations and shipping labels
08

Rosistem RFID Encoder

.NET component that writes data to the RFID tag when the label is printed.

  • Encode a tag on a given printer, or encode and print
  • Languages: Zebra ZPL II, Datamax DPL, Cognitive; custom command
  • Text, hexadecimal or binary input, with built-in conversions
  • Prefix / suffix for the encoder command
  • Optional printing of encoded data and diagnostics
  • Visual Basic sample included
09

Barcode fonts

Fonts for reporting tools that only work with text.

  • Code 39, Code 39 Extended, Code 39M
  • Code 128, EAN-128, EAN-13, Code 2 of 5
  • Data Matrix and PDF417
  • Dedicated installer
10

MICR encoding

Font and component for MICR characters on financial documents.

  • For cheques and other payment instruments
  • Included in the Reporting Services component
  • Printing on cheque printers with MICR support
11

PDF Directory Printing

Utility that watches a folder and sends every new PDF to the configured printer.

  • Invoices, shipping labels, documents generated by back-end systems
  • No manual opening of each file
  • One printer configured per folder
12

REST API and .NET SDK

The Rosistem WMS API documented with OpenAPI, with a typed C# client generated from the specification.

  • Swagger UI for exploring the API
  • One client class per controller (e.g. ProductsClient, DocumentsOutClient)
  • Asynchronous methods with paging and search
  • Errors reported with HTTP status and response body
  • openapi-v1.json specification shipped in the package

FOR YOUR TEAM

Each role has a clear part in the process.

Developer

Integrates the component and binds its properties to data.

Software architect

Checks platform, version and the identifier generation point.

Testing team

Validates content and reading on representative documents.

FITTED TO YOUR OPERATION

One product.
Your working context.

How we plan implementation ↗

Desktop applications

Barcodes as interface elements.

Web applications

Generation using a family compatible with the project platform.

Documents and reports

Document data converted into scannable identifiers.

CONTROL AND CONFIDENCE IN DATA

Know what enters the process.
Check what comes out.

Operational reliability relies on correct identification, explicit checks and records that can be reviewed. These are the solution’s control points.

Runtime

Input data
Platform, version and architecture
Check
The component family is selected for the specific application.
Outcome
Integration suited to the chosen environment.

Code content

Input data
Data and symbology
Check
Format and dimensions are checked using representative data.
Outcome
Identifiers suitable for the application workflow.

Documents and reports

Input data
Fields and data sources
Check
Code generation is linked to document data.
Outcome
Scannable information in the generated output.

RFID and equipment

Input data
Reader, tag and encoding
Check
Interaction is tested with the project equipment and materials.
Outcome
A validated identification or encoding workflow.

Project analysis also establishes access, data retention and operational continuity requirements. Configuration and responsibilities are documented for the environment where the solution will be used.

INTEGRATIONS AND EQUIPMENT

Environments, reports, equipment and symbologies

Development environments, reporting engines and equipment the components work with.

Development environments

  • Visual Studio (.NET: WinForms, WPF, ASP.NET)
  • Delphi / C++ Builder (VCL)
  • Eclipse / IntelliJ (Java)
  • PHP: Laravel, Symfony or plain PHP
  • Classic Visual Basic and Office (ActiveX)

Reports and documents

  • Crystal Reports
  • Reporting Services / RDLC
  • Microsoft Excel, Word, PowerPoint, Access

Equipment

  • Any printer installed in Windows
  • RFID label printers (Zebra ZPL II, Datamax DPL)
  • Cognitive RFID encoders
  • Cheque printers with MICR support

2D and GS1 symbologies

  • Data Matrix
  • QR Code / Micro QR
  • PDF417 / MicroPDF417
  • Aztec Code
  • MaxiCode
  • GS1-128
  • GS1 DataBar (including Stacked, Expanded)
  • GS1 Composite

Specialised symbologies

  • HIBC (Code 128, Code 39, Data Matrix, QR, PDF417, Aztec)
  • PZN, Pharmacode
  • Royal Mail 4 State, Australia Post, USPS OneCode, PLANET, POSTNET
  • Deutsche Post Leitcode / Identcode, KIX, Japan Post, Korea Post
  • ITF-14, EAN-14, NVE-18

Code sample (VB.NET)

  • Dim bcLinear As New Rosistem.Barcode.Controls.LinearControl
  • bcLinear.Symbology = Rosistem.Barcode.Symbologies.Code93
  • bcLinear.TextToEncode = "1234567890123"
  • bcLinear.Resolution = Rosistem.Barcode.Resolutions.Custom
  • bcLinear.ResolutionCustomDPI = "300.00"

Code sample (C#, .NET SDK for the API)

  • var http = RosistemWmsApi.CreateHttpClient(baseUrl, apiKey);
  • var products = new ProductsClient(http);
  • var page = await products.ProductsGETAsync(page: 1, pageSize: 50, search: "ART-");

WHAT CHANGES

Codes generated by a component, not composed by hand

AspectWithout a dedicated solutionWith Barcoding
Code generationText formatted with a barcode font, with encoding rules written in the applicationThe component encodes the data and calculates check characters
Print qualityOutput depends on the font installed on the workstationRaster or vector image at the printer resolution
ReportsCodes added separately from the document dataThe code is bound to the report fields
RFID labelsTag encoded separately from label printingTag written from the application when the label prints
PDF documentsEach PDF opened and printed by handWatched folder, automatic printing on the configured printer

TECHNICAL SHEET

Platforms, output, licensing and support

.NETWinForms, WPF, ASP.NET, Reporting Services / RDLC; C# and VB.NET samples
ActiveXActiveX hosts: Visual Basic, Access, Word, Excel, PowerPoint
Delphi / VCLDelphi 6, Delphi 7, XE7, RAD Studio 10.2; C++ Builder
JavaClasses for 1D and 2D codes; servlet for server-side generation
PHPClass library, no native dependencies
OutputRaster or vector image; rotation, quiet zone, human-readable text, check digits
RFID.NET component; Zebra ZPL II, Datamax DPL, Cognitive or custom command
API and SDKREST, documented with OpenAPI (Swagger UI); C# client for netstandard2.0 and net8.0
LicensingPer application (redistribution with no end-user limit) or per developer (up to 3 commercial applications); no per-unit royalties
Evaluation30-day trial licence with no functional limitations
Support12 months of e-mail technical support and updates included in the licence

IMPLEMENTATION AND ADOPTION

From a demonstration to a workflow your team can use.

A complete project includes data, equipment, people and acceptance criteria. Every stage has a concrete outcome to review before moving forward.

  1. 01

    Process discovery

    We define operations, responsibilities, data and the intended outcome.

    DeliverableDocumented workflow and project scope

  2. 02

    Data preparation

    We review identifiers, field structure and the examples to be used in the trial.

    DeliverableRepresentative data and scenarios

  3. 03

    Configuration and integration

    We define equipment, data exchanges and operating rules for the agreed workflow.

    DeliverableConfiguration ready for validation

  4. 04

    Validation on a real workflow

    We run the complete operation, including exceptions and result verification.

    DeliverableAcceptance criteria checked

  5. 05

    Training and launch

    The team practises role-specific operations. We establish a pilot workflow and launch responsibilities.

    DeliverableTrained team and operating procedure

  6. 06

    Support and evolution

    We agree issue reporting procedures and priorities for subsequent phases.

    DeliverableAgreed responsibilities and next steps

EVALUATE A REAL SCENARIO

A demonstration should answer your project’s questions.

A representative document, its data and the runtime environment: we check code generation, display or printing and reading of the result.

Prepare a demonstration with the Rosistem team ↗

YOUR NEXT STEP

What technology do you use, and where should the code appear?

Discuss your integration ↗
See the project stages →

PRODUCT PRESENTATIONS

More context for your decision.

MORE MATERIAL

Developer components page

FREQUENTLY ASKED QUESTIONS

The details that matter before your project.

Which component family should we choose?

We start with the project platform: .NET, ASP.NET, Delphi/VCL, Java, PHP or ActiveX. Compatibility with the environment version and application deployment model is confirmed before selection.

Can we include barcodes in reports?

Yes, dedicated families allow barcodes in documents and reports. We check the reporting engine, data binding and printed output using an example from your project.

What information is needed to select a component?

The language, platform and version, symbologies, reporting engine if used, and how the application will be distributed.

How do we connect company data?

We define the data source, required fields and expected output. Import and export formats or available interfaces are validated for the selected version before launch.

How does implementation work?

We begin with workflow and equipment discovery, configure a pilot scenario and review the results with your team. After training, we agree responsibilities and rollout stages.

What determines duration and cost?

They depend on features, the number of workstations, equipment, adaptations and required data exchanges. A proposal is prepared after these requirements are clarified.

Does one component cover every platform?

No. Each platform has its own component family. We confirm the family, runtime version, architecture and required functions for the specific project.

Can we test a component before buying?

Yes. The 30-day trial licence has no functional limitations, so the component can be tested in the real project.

LET’S TALK ABOUT YOUR PROJECT

See the solution in your business context.

Tell us about your operations, equipment and what you want to improve. The Rosistem team will contact you to discuss a suitable configuration.

For a focused discussion
Your platform, development environment version, symbologies and a sample report.

Barcoding

sales@rosistem.com
+40 721 370 157

Fields marked * are required. Do not include passwords or confidential information in your message.

Discuss your project with us

You can control external video loading. We do not use first-party analytics or marketing tools.

Read the cookie policy