Hello Michael,
Thanks for using our products.
I have tested the scenario while converting inv.pdf and I am unable to notice any problem. As per my observations, the resultant image file as identical to source PDF document. For your reference, I have attached the resultant image file that I have generated using Aspose.Pdf for .NET 6.1.0.
More along, I have also tried converting broc.pdf and I am able to notice same problems. For the sake of correction, I have logged this problem as PDFNEWNET-30292 in our issue tracking system. We will further look into the details of these problems and will keep you updated on the status of correction. We apologize for your inconvenience.
Hello Michael,
Thanks for your sharing the details.
We are testing the scenario using .Net4.0 and .Net3.5 version of product and will get back to you soon. Please be patient and spare us little time. We are really sorry for this inconvenience.
Hello Michael,
Thanks for your patience.
I have investigated this issue in further details and have observed that the problem is occurring when using Aspose.Pdf.dll from .net4.0 and .net4.0_ClientProfile folders. For the sake of correction, I have logged this problem as PDFNEWNET-30346 in our issue tracking system. We will further look into the details of this problem and will keep you updated on the status of correction. Please be patient and spare us little time. We apologize for your inconvenience.
The issues you have found earlier (filed as 30346 ) have been fixed in this update.
This message was posted using Notification2Forum from Downloads module by aspose.notifier.
The issues you have found earlier (filed as PDFNEWNET-30292) have been fixed in this update.
This message was posted using Notification2Forum from Downloads module by aspose.notifier.