01 / .NET
Components for .NET applications.
Integration into .NET applications and services to generate identifiers and include them in documents.
Explore capabilities ↗Barcode and RFID components
Components for developers: generate barcodes in applications, reports and services. Choose the right family for .NET, ActiveX, Delphi, PHP or Java.
Software · Equipment · Implementation
FROM YOUR APPLICATION DATA
WHY Barcoding
Integrate codes into your application documents and workflows. Compatibility is checked against your technology, version and required output format.
AT A GLANCE
Developer components that generate barcodes and encode RFID directly from your application, plus a REST API with a typed .NET client.
ABOUT THE SOLUTION
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
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.
THE WORKFLOW
Integration starts with choosing the component and ends with validation on real equipment; support and updates continue after delivery.
MODULES AND CAPABILITIES
Control for WinForms and WPF applications, added from the Visual Studio toolbox.
Server-side barcode generation in ASP.NET web application pages.
Barcodes in reports generated by the application, bound to the report data.
ActiveX control for compatible hosts: Visual Basic, Access, Word, Excel, PowerPoint.
VCL components for Delphi and C++ Builder, configured from the Object Inspector.
Java classes for 1D and 2D barcode generation, including server-side through a servlet.
PHP class library that renders barcode images from scripts, with no native dependencies.
.NET component that writes data to the RFID tag when the label is printed.
Fonts for reporting tools that only work with text.
Font and component for MICR characters on financial documents.
Utility that watches a folder and sends every new PDF to the configured printer.
The Rosistem WMS API documented with OpenAPI, with a typed C# client generated from the specification.
FOR YOUR TEAM
Integrates the component and binds its properties to data.
Checks platform, version and the identifier generation point.
Validates content and reading on representative documents.
Barcodes as interface elements.
Generation using a family compatible with the project platform.
Document data converted into scannable identifiers.
CONTROL AND CONFIDENCE IN DATA
Operational reliability relies on correct identification, explicit checks and records that can be reviewed. These are the solution’s control points.
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
Development environments, reporting engines and equipment the components work with.
WHAT CHANGES
| Aspect | Without a dedicated solution | With Barcoding |
|---|---|---|
| Code generation | Text formatted with a barcode font, with encoding rules written in the application | The component encodes the data and calculates check characters |
| Print quality | Output depends on the font installed on the workstation | Raster or vector image at the printer resolution |
| Reports | Codes added separately from the document data | The code is bound to the report fields |
| RFID labels | Tag encoded separately from label printing | Tag written from the application when the label prints |
| PDF documents | Each PDF opened and printed by hand | Watched folder, automatic printing on the configured printer |
TECHNICAL SHEET
| .NET | WinForms, WPF, ASP.NET, Reporting Services / RDLC; C# and VB.NET samples |
|---|---|
| ActiveX | ActiveX hosts: Visual Basic, Access, Word, Excel, PowerPoint |
| Delphi / VCL | Delphi 6, Delphi 7, XE7, RAD Studio 10.2; C++ Builder |
| Java | Classes for 1D and 2D codes; servlet for server-side generation |
| PHP | Class library, no native dependencies |
| Output | Raster 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 SDK | REST, documented with OpenAPI (Swagger UI); C# client for netstandard2.0 and net8.0 |
| Licensing | Per application (redistribution with no end-user limit) or per developer (up to 3 commercial applications); no per-unit royalties |
| Evaluation | 30-day trial licence with no functional limitations |
| Support | 12 months of e-mail technical support and updates included in the licence |
IMPLEMENTATION AND ADOPTION
A complete project includes data, equipment, people and acceptance criteria. Every stage has a concrete outcome to review before moving forward.
We define operations, responsibilities, data and the intended outcome.
DeliverableDocumented workflow and project scope
We review identifiers, field structure and the examples to be used in the trial.
DeliverableRepresentative data and scenarios
We define equipment, data exchanges and operating rules for the agreed workflow.
DeliverableConfiguration ready for validation
We run the complete operation, including exceptions and result verification.
DeliverableAcceptance criteria checked
The team practises role-specific operations. We establish a pilot workflow and launch responsibilities.
DeliverableTrained team and operating procedure
We agree issue reporting procedures and priorities for subsequent phases.
DeliverableAgreed responsibilities and next steps
EVALUATE A REAL SCENARIO
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
PRODUCT PRESENTATIONS

MORE MATERIAL
FREQUENTLY ASKED QUESTIONS
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.
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.
The language, platform and version, symbologies, reporting engine if used, and how the application will be distributed.
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.
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.
They depend on features, the number of workstations, equipment, adaptations and required data exchanges. A proposal is prepared after these requirements are clarified.
No. Each platform has its own component family. We confirm the family, runtime version, architecture and required functions for the specific project.
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
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.
sales@rosistem.com
+40 721 370 157
Fields marked * are required. Do not include passwords or confidential information in your message.