BarcodeLib vs IronBarcode: C# Barcode Library Comparison

BarcodeLib Core Generation Pattern

The standard BarcodeLib generation workflow requires creating an instance, configuring properties, and calling Encode():

// BarcodeLib
using BarcodeLib;
using System.Drawing;
using System.Drawing.Imaging;

var b = new Barcode();
b.IncludeLabel = true;
b.Width = 300;
b.Height = 100;
Image img = b.Encode(TYPE.CODE128, "PRODUCT-12345");
img.Save("barcode.png", ImageFormat.Png);

// BarcodeLib
using BarcodeLib;
using System.Drawing;
using System.Drawing.Imaging;

var b = new Barcode();
b.IncludeLabel = true;
b.Width = 300;
b.Height = 100;
Image img = b.Encode(TYPE.CODE128, "PRODUCT-12345");
img.Save("barcode.png", ImageFormat.Png);

Imports BarcodeLib
Imports System.Drawing
Imports System.Drawing.Imaging

Dim b As New Barcode()
b.IncludeLabel = True
b.Width = 300
b.Height = 100
Dim img As Image = b.Encode(TYPE.CODE128, "PRODUCT-12345")
img.Save("barcode.png", ImageFormat.Png)

This is the full generation workflow. The property-setter pattern is the design: all configuration happens on the instance before the Encode() call, and the return value is a System.Drawing.Image that must be separately saved or converted to bytes.

Detailed Feature Comparison

BarcodeLib Approach

BarcodeLib requires constructing an instance and setting properties before calling Encode(). Output is a System.Drawing.Image object:

using BarcodeLib;
using System.Drawing;
using System.Drawing.Imaging;

public byte[] GenerateCode128(string data)
{
    var b = new Barcode();
    b.IncludeLabel = true;
    b.Width = 300;
    b.Height = 100;
    Image img = b.Encode(TYPE.CODE128, data);

    using var ms = new MemoryStream();
    img.Save(ms, ImageFormat.Png);
    return ms.ToArray();
}

using BarcodeLib;
using System.Drawing;
using System.Drawing.Imaging;

public byte[] GenerateCode128(string data)
{
    var b = new Barcode();
    b.IncludeLabel = true;
    b.Width = 300;
    b.Height = 100;
    Image img = b.Encode(TYPE.CODE128, data);

    using var ms = new MemoryStream();
    img.Save(ms, ImageFormat.Png);
    return ms.ToArray();
}

Imports BarcodeLib
Imports System.Drawing
Imports System.Drawing.Imaging
Imports System.IO

Public Function GenerateCode128(data As String) As Byte()
    Dim b As New Barcode()
    b.IncludeLabel = True
    b.Width = 300
    b.Height = 100
    Dim img As Image = b.Encode(TYPE.CODE128, data)

    Using ms As New MemoryStream()
        img.Save(ms, ImageFormat.Png)
        Return ms.ToArray()
    End Using
End Function

The System.Drawing.Image return type means byte array output requires a MemoryStream intermediary. The IncludeLabel property is a boolean toggle — BarcodeLib automatically renders the encoded data string as the visible label beneath the bars.

IronBarcode Approach

IronBarcode's generation is fully static. Configuration chains after CreateBarcode(), and output methods terminate the chain directly:

// NuGet: dotnet add package IronBarcode
using IronBarCode;

public byte[] GenerateCode128(string data)
{
    return BarcodeWriter.CreateBarcode(data, BarcodeEncoding.Code128)
        .ResizeTo(300, 100)
        .AddAnnotationTextBelowBarcode(data)
        .ToPngBinaryData();
}

// NuGet: dotnet add package IronBarcode
using IronBarCode;

public byte[] GenerateCode128(string data)
{
    return BarcodeWriter.CreateBarcode(data, BarcodeEncoding.Code128)
        .ResizeTo(300, 100)
        .AddAnnotationTextBelowBarcode(data)
        .ToPngBinaryData();
}

Imports IronBarCode

Public Function GenerateCode128(data As String) As Byte()
    Return BarcodeWriter.CreateBarcode(data, BarcodeEncoding.Code128) _
        .ResizeTo(300, 100) _
        .AddAnnotationTextBelowBarcode(data) _
        .ToPngBinaryData()
End Function

.ToPngBinaryData() returns the byte array directly — no intermediate Image or MemoryStream object. .AddAnnotationTextBelowBarcode() takes the label string explicitly, giving control over what text appears below the bars. For advanced generation scenarios, see the IronBarcode barcode generation documentation.

BarcodeLib Approach

BarcodeLib has no reading API. There is no Decode(), Scan(), or ReadBarcode() method. The absence is not a version difference — reading has never been part of the library's design. Any attempt to call a decode method results in a compile error:

// BarcodeLib — reading does not exist
using BarcodeLib;

var b = new Barcode();

// This will not compile — there is no Decode or Read method
// var value = b.Decode("barcode.png");       // CS1061: no definition
// var value = b.Scan("barcode.png");          // CS1061: no definition
// var value = b.ReadBarcode("barcode.png");   // CS1061: no definition

// The only thing you can do is generate:
Image img = b.Encode(TYPE.CODE128, "PRODUCT-12345");  // this works

// BarcodeLib — reading does not exist
using BarcodeLib;

var b = new Barcode();

// This will not compile — there is no Decode or Read method
// var value = b.Decode("barcode.png");       // CS1061: no definition
// var value = b.Scan("barcode.png");          // CS1061: no definition
// var value = b.ReadBarcode("barcode.png");   // CS1061: no definition

// The only thing you can do is generate:
Image img = b.Encode(TYPE.CODE128, "PRODUCT-12345");  // this works

Imports BarcodeLib

Dim b As New Barcode()

' This will not compile — there is no Decode or Read method
' Dim value = b.Decode("barcode.png")       ' No definition
' Dim value = b.Scan("barcode.png")         ' No definition
' Dim value = b.ReadBarcode("barcode.png")  ' No definition

' The only thing you can do is generate:
Dim img As Image = b.Encode(TYPE.CODE128, "PRODUCT-12345")  ' this works

Teams that need both generation and reading alongside BarcodeLib must add a second library — typically ZXing.Net — which introduces its own dependency management burden and a second API surface to maintain.

IronBarcode Approach

BarcodeReader.Read() accepts image files, PDF files, streams, and System.Drawing.Bitmap objects. Reading from a PDF requires no additional library:

using IronBarCode;

// Read from an image
var results = BarcodeReader.Read("barcode.png");
Console.WriteLine(results.First().Value);  // "PRODUCT-12345"

// Read all barcodes from a PDF — no separate PDF library needed
var pdfResults = BarcodeReader.Read("invoice-batch.pdf");
foreach (var result in pdfResults)
{
    Console.WriteLine($"Page {result.PageNumber}: {result.Value}");
}

// Tune reading for speed vs. thoroughness
var options = new BarcodeReaderOptions
{
    Speed = ReadingSpeed.Balanced,
    ExpectMultipleBarcodes = true
};
var multiResults = BarcodeReader.Read("warehouse-scan.png", options);

using IronBarCode;

// Read from an image
var results = BarcodeReader.Read("barcode.png");
Console.WriteLine(results.First().Value);  // "PRODUCT-12345"

// Read all barcodes from a PDF — no separate PDF library needed
var pdfResults = BarcodeReader.Read("invoice-batch.pdf");
foreach (var result in pdfResults)
{
    Console.WriteLine($"Page {result.PageNumber}: {result.Value}");
}

// Tune reading for speed vs. thoroughness
var options = new BarcodeReaderOptions
{
    Speed = ReadingSpeed.Balanced,
    ExpectMultipleBarcodes = true
};
var multiResults = BarcodeReader.Read("warehouse-scan.png", options);

Imports IronBarCode

' Read from an image
Dim results = BarcodeReader.Read("barcode.png")
Console.WriteLine(results.First().Value)  ' "PRODUCT-12345"

' Read all barcodes from a PDF — no separate PDF library needed
Dim pdfResults = BarcodeReader.Read("invoice-batch.pdf")
For Each result In pdfResults
    Console.WriteLine($"Page {result.PageNumber}: {result.Value}")
Next

' Tune reading for speed vs. thoroughness
Dim options As New BarcodeReaderOptions With {
    .Speed = ReadingSpeed.Balanced,
    .ExpectMultipleBarcodes = True
}
Dim multiResults = BarcodeReader.Read("warehouse-scan.png", options)

The ReadingSpeed enum allows tuning scan performance for high-volume scenarios. For guidance on reading configuration, see the IronBarcode reading documentation.

BarcodeLib Approach

Starting with BarcodeLib 3.x, the library introduced SkiaSharp as a graphics backend to replace System.Drawing.Common, which became Windows-only after .NET 6. BarcodeLib pins to a specific SkiaSharp version range. If a project already uses SkiaSharp through another dependency — common in MAUI projects using SkiaSharp.Views.Maui and Microsoft.Maui.Graphics — the resolved version may fall outside BarcodeLib's expected range. The result is a NU1608 warning at minimum and an assembly binding failure at runtime at worst:

warning NU1608: Detected package version outside of dependency constraint:
BarcodeLib 3.1.5 requires SkiaSharp (>= 2.88.7 && < 2.89.0) but
version SkiaSharp 3.116.1 was resolved.

Forcing a resolution through explicit package references adds complexity without a guarantee:

<ItemGroup>
  <PackageReference Include="BarcodeLib" Version="3.1.5" />

  <PackageReference Include="SkiaSharp" Version="3.116.1" />
  <PackageReference Include="SkiaSharp.Views.Maui.Controls" Version="3.116.1" />
</ItemGroup>

<ItemGroup>
  <PackageReference Include="BarcodeLib" Version="3.1.5" />

  <PackageReference Include="SkiaSharp" Version="3.116.1" />
  <PackageReference Include="SkiaSharp.Views.Maui.Controls" Version="3.116.1" />
</ItemGroup>

Even with explicit overrides, compatibility depends on BarcodeLib's internal API calls matching what the pinned version exposes. There is no support contract that guarantees a fix on a schedule that matters to the project.

IronBarcode Approach

IronBarcode does not share the SkiaSharp dependency graph with application code. There is no version negotiation to manage, no NU1608 to diagnose, and no runtime assembly binding risk tied to SkiaSharp version resolution. MAUI projects, Blazor projects, and any other application that depends on SkiaSharp can install IronBarcode without any version conflict. For MAUI-specific integration patterns, see the IronBarcode MAUI documentation.

Reading Requirement Appears

A system that has generated shipping labels for months receives a new requirement: the application must also process returned labels from suppliers. The warehouse integration needs to parse barcodes from inbound shipment manifests. A document management system needs to index barcodes on scanned PDFs. BarcodeLib cannot fulfill any of these requirements — the reading API does not exist. The team evaluates adding ZXing.Net alongside BarcodeLib, weighs the dual-library maintenance burden and the two separate dependency graphs, and decides the cleaner path is a library that handles both generation and reading under a single NuGet install.

SkiaSharp Conflict in a MAUI Project

A team adds BarcodeLib to an existing MAUI application and immediately encounters NU1608 warnings during restore. They investigate, identify the version mismatch between BarcodeLib's expected SkiaSharp range and the version MAUI requires, add explicit <PackageReference> overrides to force a resolution, and get the build to pass. Then they encounter a runtime crash on device when SkiaSharp's native binaries load the wrong version. The fix requires deeper investigation into the assembly binding log. Switching to IronBarcode removes the conflict at the root — not by finding a compatible SkiaSharp version, but by eliminating the shared dependency entirely.

PDF Barcode Processing Required

Applications that generate PDF documents with embedded barcodes — invoices, work orders, shipping manifests — sometimes need to read those barcodes back during downstream processing. BarcodeLib generates barcode images but has no PDF support on either end. Reading barcodes from a PDF with BarcodeLib requires rendering the PDF to images first using a separate PDF library, then passing those images to a separate reading library. IronBarcode handles the full chain natively: BarcodeReader.Read("file.pdf") traverses every page and returns all detected barcodes without an intermediate rendering step.

QR Code Features Outgrow Basic Generation

Projects that initially required only basic QR code generation often evolve to need logo embedding, color customization, or error correction level configuration. BarcodeLib supports QR codes through TYPE.QR_Code but provides no options beyond the standard Width, Height, and IncludeLabel properties. IronBarcode's QRCodeWriter exposes logo embedding, color control, and error correction tuning through chained methods. Teams whose QR code requirements have expanded past what BarcodeLib's basic implementation supports find that the feature gap drives the migration decision.

Instance API to Static Fluent API

BarcodeLib code uses a mutable object pattern: create a Barcode instance, set properties, call Encode(). IronBarcode uses a static fluent pattern: call BarcodeWriter.CreateBarcode(), chain configuration methods, terminate with an output method. Existing code that stores a Barcode instance as a field or passes it between methods will need restructuring. The typical change is replacing the property-setter block with a method chain:

// The property setters on b become chained methods
BarcodeWriter.CreateBarcode(data, BarcodeEncoding.Code128)
    .ResizeTo(300, 100)
    .AddAnnotationTextBelowBarcode(data)
    .SaveAsPng(outputPath);

// The property setters on b become chained methods
BarcodeWriter.CreateBarcode(data, BarcodeEncoding.Code128)
    .ResizeTo(300, 100)
    .AddAnnotationTextBelowBarcode(data)
    .SaveAsPng(outputPath);

System.Drawing.Image to Direct Output

BarcodeLib returns System.Drawing.Image, which requires MemoryStream to produce bytes. Any code typed to Image or System.Drawing.Image will need updating. IronBarcode's fluent chain terminates with the desired output format directly — .SaveAsPng(), .ToPngBinaryData(), .ToAnyImageData() — removing the need for the intermediate image object and the MemoryStream step.

TYPE Enum to BarcodeEncoding Enum

BarcodeLib uses the TYPE class with uppercase constants such as TYPE.CODE128. IronBarcode uses the BarcodeEncoding enum with PascalCase values such as BarcodeEncoding.Code128. The values map directly. A grep for TYPE\. across .cs files identifies all occurrences that need updating, and a systematic find-and-replace covers the common formats: CODE128 → Code128, EAN13 → EAN13, UPCA → UPCA, QR_Code → QRCode.

SkiaSharp Reference Cleanup

Projects that added explicit <PackageReference Include="SkiaSharp"> entries only to resolve BarcodeLib's NU1608 warnings can remove those overrides after switching to IronBarcode. The dotnet list package --include-transitive command confirms whether SkiaSharp is still required by other packages in the project before removing it.