Monday, July 6, 2015

Encode Barcode with Empty Bars, QR & Micro QR Codes Encoding inside .NET Apps

What’s new in this release?

We are happy to announce the new release of Aspose.BarCode for Reporting Services 7.0.0. This new release covers some new barcode symbologies. It provides full support for Microsoft SQL Server 2014, enhances its support in the Business Intelligence for Visual Studio 2013 report building and allows clients to encode barcode with empty bars. Along with these features support, we have included many other recent fixes reported by our clients in the Aspose site forums. For the smallest possible code users might want to consider a micro QR code because the Micro QR code is a smaller version of the QR code standard for applications where symbol size is constrained. We have added its encoding support. Many other improvements are added to QR encoding. Users can now encode QR codes in ECI mode. It also encodes a multi-ECI and FNC1 symbols. We have added full support of Microsoft SQL Server 2014. Users can now develop their reports. For Microsoft SQL Server 2014, we have provided two separate assemblies. First “Design Version” works only with designers (Visual Studio or BIDS). This assembly is located in the Bin\SSRS2014\DesignVersion directory. Second “RunTimeVersion” works only with the report server. This assembly is located in the Bin\SSRS2014\RunTimeVersion directory. We noticed some queries from our clients in using Aspose.BarCode APIs with Business Intelligence for Visual Studio 2013. Since, we checked its support and have fixed some issues. Toolbox in Visual Studio 2013 can’t detect any report component. We have already addressed this issue for Visual Studio 2012. It’s now documented in our docs. We have added a new FilledBars property in BarCodeBuilder class. It allows clients to generate filled or not filled bars. This property works only with 1D barcodes. We have enhanced OneCode and SwissPostParcel encoding areas. Already, clients had the capacity encode off base content in OneCode symbology but now it displays a proper error message. Similarly, in case of SwissPostParcel code, Aspose.BarCode APIs were adding “98″ text at the start whereas parcels always start with “99.42″. We have fixed it. This release also comprise a number of other key fixes that help us in writing capabilities, some of them are Can’t create Code128 barcode with standard ‘f’ character, Incorrect encoding punctuation in PDF417 and MicroPDF417 barcodes, Index out of range error message while generating a Code128 symbology, XDimension property is not working as expected and several other. Below is the list of new and improved features added in this new release
  • Add generation with empty bars
  • Add support of SQL Server 2014 to Aspose.BarCode for Reporting Services
  • Check support of Business Intelligence for Visual Studio 2013
  • Can't create Code128 barcode with standard 'f' character
  • Incorrect encoding punctuaion in PDF417 and MicroPDF417 barcodes
  • Index out of range error message while generating a Code128 symbology
  • Add encoding support of Micro QR code
  • Same size OneCode barcodes are being generated
  • XDimension property is not working as expected
  • Parcels always start with 99.42 whereas Aspose SwissPostParcel symbology adds 98 in start
Overview: Aspose.Report for .NET

Aspose.BarCode for Reporting Services is a .NET solution for the rendering of barcode images in SQL Server 2000, 2005 & 2008 Reporting Services. It supports 29+ linear (1D) and 2D barcode symbologies including MacroPdf417, Australia Post, OneCode, Code128, Code39, PDF417, UPCA, Codabar, MSI and QR etc. Also render barcode images on reports in BMP, JPG, PNG and GIF formats. Other features include EAN-128 application identifiers, DPI resolution settings, barcode size and location adjustments.


No comments:

Post a Comment