We’re using Aspose Barcode for Reporting Services on SSRS 2005 platform. Everything was fine till our customer needed to get report outputs also as high resolution TIFF files. Because Aspose Barcode’s dpiX and dpiY properties are set to 96 (it should be for pdf), when we get 300 dpi TIFF output using ServerRport.Render method by sending DeviceInfo xml structure, we get a tiny barcode because it’s drawn for 96 dpi. (Sample: 300300)
As you can see we can not change dpi of barcode to 300 dpi because we need 96 for some cases and adding this dpi information as report parameter is not an option in our case. So what we need is, the barcode component get dpi information from rendering engine dynamically. Is this possible? Or is there a workaround for our case?
Thanks for your interest about issue. Is there any progress on this? My customer is pushing me to provide a solution since they need to send some sort of files to printery.
If you need, I can provide sample TIFF and PDF files about this. I’ve a set of TIFF files saved in different resolutions and a PDF version of regular file. I want to send files thru e-mail, thus files include private data of customer…
Aspose.barcode supports setting the DPI by using the designer or editing the .RDL file directly. The attached image is the screenshot of using the designer, and below is the example of editing the RDL file:
_Note: XML contents excluded for brevity.
Please take a look at the fully rendered example were imported into designer.
Setting the DPI by using SSRS’s configuration file is not supported in the current version, but I think it’s a good point, and our developers will do more research to estimate if it can be added as a new feature in the next version.
Thanks for the response. However I’ve already aware of this dpi setting functionality. The problem is that I need the barcode component to decide correct dpi, by using the renderer’s active resolution…
As I understand, there is no option for us currently about this. Thanks for your kind interest on the issue. You’re right, it would be a great feature if component can get the resolution property from rendering engine and use it by default…