Barcode Professional for XAML WinRT Windows Store Apps just released!

Barcode Pro for XAML WinRT (Windows Store Apps)

Today is great day! We’re proud to announce that our new Barcode Professional for XAML WinRT is now available!

You can start using Barcode Professional for XAML WinRT in your Windows Store Apps for adding barcode printing and generation capabilities. Barcode Pro for XAML WinRT can be used within Windows Store Apps developed with VB, C# or C++ in Visual Studio 2012 or the Expression edition for Windows 8!

Feel free to contact our experts for any kind of questions on our products.

Porting Barcode Professional to Windows 8 WinRT API

Our team has not stopped since the WebClientPrint product release and this time they are working on porting our first-class Barcode Professional product to the new Windows 8 WinRT API.

Neodynamic is the only company specialized in barcode technologies which provides GS1/ISO-IEC/AIM-compliance linear (1D), postal, 2D, stacked and composite barcode symbols to .NET developers and the new Windows Store applications market will need a first-class barcode solution for sure.

Let’s say you need to create high quality QR Code to stamp it on gift cards, invoices, etc within your Windows Store app. Or maybe you need to create and print barcode labels within your Windows Store app. Or the business reports need some kind of barcode being there. For any barcode needs you might have when developing your Windows Store apps, you can safely leverage them to Neodynamic’s Barcode Professional for XAML WinRT product.

The product will be available shortly so stay tuned!

Need to add barcodes in SQL Reporting Services 2012?

We’re proud to announce the availability of Barcode Professional 7.0 for the latest Microsoft SQL Server Reporting Services 2012! Barcode Professional for SSRS is the first third-party barcode solution supporting RS 2012 version.

Barcode Professional for RS brings you a new Barcode CRI (Custom Report Item) for supporting SQL Server Reporting Services 2012 edition which you can use within Visual Studio 2010 or the new SQL Server Data Tools 2012 (formerly Business Intelligent Development Studio a.k.a. BIDS) for adding high quality barcode images into your RDL server reports.

Barcode Professional supports most popular Linear (1D), Postal, MICR & 2D Symbologies/Standards all-in-one solution including Code 39, Code 128, GS1-128, GS1 DataBar (RSS-14), EAN 13 & UPC, Postal (USPS, British Royal Mail, Australia Post, DHL, etc.), Data Matrix, QR Code, PDF 417, Aztec Code, UPS MaxiCode, MICR E-13-B Characters, ALL EAN/UPC Composite Barcodes (CC-A, CC-B & CC-C) and many more barcode standards.

How to get it? Just download the installer from

NOTE: Customers who bought Barcode Pro 7.0 for RS will get this update for free i.e. at no extra costs!!!

ThermalLabel SDK 4.0 Updated – XML Template bug

Our team just released a new maintenance release of ThermalLabel SDK 4.0 containing the following bug fixes:

  • When exporting the thermal label to XML Template, Font params are incorrect.
  • Failed to import or load an XML Template file.

The new version numbers of Neodynamic.SDK.ThermalLabel.dll is now as follows:

  • File Version: 4.0.3500.5
  • Assembly Version: 4.0.3500.0 (unchanged)

Update your system now by downloading and installing it from our website or using the link found in the license email you have received.

Printing small text on thermal printers at 203 dpi with ThermalLabel SDK 4.0 for .NET

If you are targeting Zebra thermal printers with 203 dpi output resolution and are using our ThermalLabel SDK 4.0, then you should take a look at this demo/guide our team has just published: How to print small text on Zebra ZPL-EPL thermal printers by using ThermalLabel SDK for .NET

In that guide, our team outlines the usage of Pixel/Bitmap TrueType Fonts on the new TextItem class for getting crisp and clear output printing at 203 dpi printers when rendering very small texts i.e. text which font size is about 0.04 inch (about 1 millimiter) high.

ThermalLabel SDK 4.0 just released!

Neodynamic is proud to announce the availability of ThermalLabel SDK 4.0 for .NET Framework!

After six months of hard work, the new ThermalLabel SDK engine v4.0 is ready for production code. We want to thank to all our customers who provided us with great feedbacks for this new release. The following is the main new features you will find in v4.0!

  • New! A complete and re-written labeling engine
  • New! An unified object model which will allows you to create ONE label and print it to either ZPL or EPL printer getting the SAME output printing!
  • New! Added preview thermal labels without needed a physical printer. It is useful for testing as well as developing.
  • New! Added Print Orientation feature. You can now print ThermalLabel objects in Portrait and Landscape orientation with 90, 180 & 270 degrees rotation
  • New! Added exportation of PrintJob & ThermalLabel objects to raster images in formats like PNG, BMP, GIF, JPEG & TIFF (including multipage TIFF)
  • New! Added exportation of PrintJob & ThermalLabel objects to Adobe PDF without the need of any third-party software
  • New! Added Caching feature to ThermalLabel items to improve printing performance
  • New! A new BarcodeItem object with lots of new features
  • New! Added a new dithering method for auto-thresholding based on Otsu method. It is used for ImageItem objects
  • New! You can print or send commands to a stream object
  • New! Added Buffering feature to PrintJob class. Buffering allows you to control how the processed printer commands in the PrintJob object are sent to the printer.
  • New! You can now specify the printer name as well as the connection timeout when using network printing

In the next couple of weeks we’ll be publishing lots of demos and guides highlighting these new features. We’re very excited with this new version and hope it helps our customers with their thermal printing needs.

kick it on

ThermalLabel SDK 4.0 almost complete!

We’re very exited about what our team will deliver in v4.0 of ThermalLabel SDK. Today we want to provide some insights while designing and developing this new version.

First step: which .NET Framework version to target?

The first thing to determine for v4.0 was which .NET Framework version our product would leverage on. Back on October last year, we decided to run a very simple survey asking our customers about on which version of .NET Framework they were using ThermalLabel SDK. The result was the following:

  • .NET 2.0 – 16%
  • .NET 3.5 – 68%
  • .NET 4.0 – 16%

Since its first release, ThermalLabel SDK was built on.NET 2.0. However, in v4.0 we had to decide which one to develop on. As we outlined in our previous post about ThermalLabel SDK 4.0 future plans the key for this new release is the change in the core engine which now should be graphic based for more development benefits. After analyzing pros and cons on .NET versions features, our team opted for .NET 3.5 and priorizing the “Client Profile” edition introduced in such .NET version. So, v4.0 of ThermalLabel SDK will require .NET 3.5 Client Profile or greater.

Brief intro to v4.0 features

Big new features and changes were made on v4.0. Most of the features outlined in our first post on v4.0 will be delivered. Here are some of them:

  • A new label graphic-based engine: this new engine allowed us to accomplish most of the other high requested features like landscape printing and export labels to raster image files. However, the new engine is not purely graphic-based. To improve printing performance, some items are generated as native printer commads and not graphics depending on the items’ settings. But this new engine will allows you to create labels which will be printed exactly to both ZPL or EPL printers! That means you no longer will need to create separated labels for targeting each printer language.
  • A complete new barcode engine: The new BarcodeItem now is based on our Barcode Professional product providing some new featues which were impossible to bring by using native printer commands.
  • Buffering: previous version of ThermalLabel worked by buffering all the printer commads before sending them to the printer. In v4.0 this is a feature which can be enabled/disabled anytime (by default it is disabled i.e. the printer commands are sent as soom as possible to the target printer).
  • Caching: because the new graphic-based engine, we included Caching feature to all items. This allows to cache the output of items to the printer once and then re-use them without re-generation. This is especially useful for items which display static contents like Company logos or fixed messages. By default, Caching is disabled.
  • Portrait and Landscape Printing: this new release will provide Portrait printing with 0 and 180 degrees rotation as well as Landscape printing with 90 and 270 degrees rotation!
  • Print Preview and Exporting Labels to image files: you no longer will need a real physical thermal printer for developing! In v4.0 you can export/save a PrintJob and ThermalLabel objects to raster image formats like JPEG, PNG, BMP, GIF and TIFF (including multi-page tiff)! You can save to files or streams and can be easily displayed on Windows Forms for end-user print preview.
  • Exporting Labels to Adobe PDF document: In addition to export labels to raster image formats, in v4.0 you can export/save a PrintJob and ThermalLabel objects to Adobe PDF documents out-of-the-box!

NOTE: The only feature we won’t be able to deliver this time is the “Visual Label Designer”. This is because we wanted to launch and test the new label engine before going forward. We have some prototypes of this which will be fine-tuned and enhanced depending on the feedbacks we get with v4.0

Breaking changes and No Backward compatibility, sadly

Because the big changes introduced in v4.0, this new release has some breaking changes and will no be backward compatible, sadly. In v4.0 we had to deprecate/remove some items which do not make sense in this release.

  • TextItem and GraphicTextItem: All text in v4.0 is graphic based now, so in oder to simplify things, then new TextItem class now features most of the goodies (full Unicode support, RTL, Windows TTF files, etc) found on previous GraphicTextItem. The last one will be deprecated/removed from v4.0
  • BarcodeItem: this item, which is now based on our Barcode Professionl product, has changed some properties and added new ones. Some of them are the ability for centering barcodes inside its specified area, text alignment including justifying, stretching barcodes, etc.
  • TableShapeItem: this item is no longer available. It was deprecated because the new TextItem and BarcodeItem classes now provide Border features which in conjunction make it possible to reproduce a table layout.


The new v4.0 of ThermalLabel SDK will provide lots of new features which will make easy working when dealing with Thermal Printers from .NET
We expect to launch it ending this month and hope our customers like and enjoy it. As allways your feedbacks are welcome and very appreciated.

Encoding Unicode in 2D barcode like PDF417, DataMatrix, QRCode or AztecCode

Try encoding Unicode characters in 2D barcodes like PDF417, DataMatrix, QRCode or AztecCode is a challenge because all those standards were not designed to encode Unicode two-byte characters but single-byte strings only.

In a recent guide (with a sample code in VB and C# – Windows Forms), we tried to provide some tips about how to accomplish that in a “reliable way”. The “reliable” word here is very important because there’re many methods for encoding Unicode in barcodes but few of them are, precisely, reliable. We found a simple one leveraging Base64 algorithm.

NOTE: Although the guide was written by using Barcode Professional SDK for .NET, it can be applied to other editions of our products i.e. ASP.NET, Windows Forms, WPF, Reporting Services, etc.)

Encoding Unicode chars in 2D barcodes PDF417-DataMatrix-QRCode-AztecCode in VB-C#