When the reporting engine does not support the required barcode type natively, teams usually work around it with separate barcode libraries, pre-rendered images, custom scaling logic, and additional testing across platforms. That adds glue code around the reporting pipeline and makes the workflow harder to maintain, migrate, and validate.
With List & Label Cross Platform 31.003, barcode support has been expanded significantly. More report and label scenarios can now be rendered directly in the Cross Platform engine, without delegating barcode generation to external components or pre-rendered images.
What is new in List & Label Cross Platform 31.003
List & Label Cross Platform 31.003 adds native support for additional barcode types directly in the Cross Platform engine.
The update includes several GS1 DataBar variants:
GS1 DataBar GS1 DataBar Truncated GS1 DataBar Stacked GS1 DataBar Stacked Omni GS1 DataBar Limited GS1 DataBar Expanded
It also adds support for:
MaxiCode MaxiCode/UPS
In addition, the release expands support for a broader set of postal, product, pharmaceutical, and logistics-oriented barcode types:
FIM Pharmacode MSI Code11 Postnet Japanese_Postal IntelligentMail ISBN EAN14 UCC14 SCC EAN128_Full Rm4ACC_CRC DP_Leitcode DP_Identcode German_Parcel PZN PZN8
Why this matters for .NET backends
List & Label Cross Platform is built for automated, server-side report generation in .NET applications — from backend services and cloud workloads to containers and CI/CD-driven document generation.
In that setup, the ideal workflow stays simple:
Application data → Report template → Export
Unsupported barcode types can break that flow and force teams into a more complex pipeline:
Application data → External barcode generation → Image handling → Report template → Export
With the expanded barcode support in 31.003, more templates can remain self-contained. The application provides the data, the report template defines the barcode, and List & Label handles the rendering.
For .NET teams, this means cleaner application code, fewer external rendering dependencies, more portable templates, and clearer ownership between application logic and report layout. It can also simplify migrations from classic List & Label projects when existing templates already use one of the newly supported barcode types.
Extended barcode content handling
List & Label Cross Platform 31.003 also improves barcode content handling for PDF417, QR, and MaxiCode.
The release adds support for encoded content patterns such as:
{binary:...}
~dNNN
~hXX
~~
This is useful when barcode values are not just plain text. Some workflows require encoded control characters, binary payloads, or structured content. Handling these cases directly in the reporting layer makes the overall pipeline easier to reason about and easier to test.
Developer takeaway
List & Label Cross Platform 31.003 expands barcode support so more real-world report and label templates can be rendered directly in cross-platform .NET reporting workflows.
For .NET developers, this means fewer external barcode generators, fewer pre-rendered images, and fewer special cases in application code.
You build the application logic. List & Label handles the reporting layer — including more of the barcode rendering that previously required workarounds.
If your current reporting pipeline generates barcode images outside the report, 31.003 is a good reason to check whether that code still needs to exist.
Leading the development at combit as Managing Director. Microsoft .NET enthusiast driving innovation & agile project management. Used to be a physicist in my first life. I love hiking and vanlife.
