Print ESC/POS commands from ASP.NET right to the client printer

We’ve just published a new article about How to print raw ESC/POS commands from ASP.NET directly to the client printer that shows you how to get fast printing outputs with dot-matrix, impact, thermal or inkjet printers that support ESC/POS-compatible commands. The article shows you how to create ESC/POS commands for a simple receipt and how to get it printed from ASP.NET right to the client printer. Works with any popular browser (Chrome, IE, Firefox, Safari, Opera) on Windows, Linux or Mac!

 A Sample Receipt printed from ASP.NET and created by using ESC/POS commands

Advertisements

WebClientPrint 2.0 for ASP.NET Update – Fixed WCPP Detection for IE v10 & v11

We’re glad to announce a new update to WebClientPrint 2.0 for ASP.NET. This new update includes:

[Fixed!] WCPP detection fails for Internet Explorer v10 or v11 clients if WCPP is not installed.

This update requires the installation of the server software only.

Download WebClientPrint 2.0 for ASP.NET server component

The “File version” values for this update are:

> Neodynamic.SDK.WebClientPrint.dll patched to v2.0.2013.1125

WebClientPrint 2.0 for ASP.NET Update – Fixed WCPP Detection for IE clients

We’re glad to announce a new update to WebClientPrint 2.0 for ASP.NET. This new update includes:

[Fixed!] WCPP detection was fixed for Internet Explorer clients to provide the exact WCPP version the client has installed.

This update requires the installation of the server software only.

Download WebClientPrint 2.0 for ASP.NET server component

The “File version” values for this update are:

> Neodynamic.SDK.WebClientPrint.dll patched to v2.0.2013.1114

jQuery ajax request error Status 0 on SSL-HTTPS when using Opera or Safari

Today we were testing our WebClientPrint for ASP.NET vNext and found an issue with jQuery Ajax requests on HTTPS but just when using Opera or Safari as the code worked just fine with IE, Chrome & Firefox.

In short the issue was this. The URL we specified to jQuery $get() contained the port number for HTTPS which is 443. Something like this $.get('https://localhost:443/something.aspx', function (data) { ... });

Again, that code worked just fine with IE, Chrome & Firefox but when using Opera or Safari, the Ajax error was “Status 0”. Removing the port number 443 from the URL fixed the issue on those browsers. HTH,

How to print barcode labels to client-side Zebra thermal printers from ASP.NET

Print barcode labels to users’ Zebra thermal printers from ASP.NET (or any web server technology) is not an easy task. There are a couple of ways to try out but all share this workflow:

  1. User enters the webpage using his favorite browser (IE, Mozilla Firefox, Google Chrome, Opera, etc.)
  2. The webpage displays the barcode label in some “format”, let’s see:
    1. No Plugin approach:
      • A simple HTML markup with <img> tags for barcodes and other common tags for text
      • One single <img> tags where the barcode and text is on it
    2. Plugin approach:
      • A PDF file containing the barcode and text
      • A Flash swf file containing the barcode and text
      • A Silverlight applet containing the barcode and text
  3. User prints the barcode label depending on the approach used in #2:
    1. For No Plugin approach, the “print page” functionality of the user’s browser is in charge.
    2. For Plugin approach, the “printing API” of the selected plugin platform (Adobe PDF Reader, Flash or Silverlight) is in charge.

Each of the above combinations has its pros and cons, for instance:

  • No Plugin approach
    • Pros: it does not require the user to have installed any Plugin on his machine
    • Cons: because this approach leverages the “print page” functionality of the user’s browser, it requires lots of effort from both, the developer and the user, to configure and fine tune all stuff to get barcode label content correctly printed on thermal printers
  • Plugin approach
    • Pros: in general, the “printing API” provided by the Plugin is more rich and customizable from the developer perspective. This allows the barcode label content to be correctly printed on the user’s thermal printer with almost any intervention or configuration from the user.
    • Cons: the user is forced to install the selected Plugin on his machine. Note: this is not always a restriction because Acrobat PDF Reader or Flash are widely installed out there.

Well after some tests here at Neodynamic, we have found the Plugin approach using Adobe PDF to be one of the most reliable ways to get your barcode labels printed on user’s thermal printers accurately. We have just published a guide providing some sample code about this topic using our ThermalLabel SDK 4.0 in ASP.NET client-side printing scenarios

kick it on DotNetKicks.com