Hashing MD5 Content Change of Processed Image in version 22.12.0 of Aspose.Imaging and ASPOSE.PDF in

Aspose.Imaging Product Family
1

We are using ASPOSE.Imaging and ASPOSE.PDF to convert PDF and Image files to Gray Scale Image in PNG format.

We store the gray scale images in the Azure Blob Container.
We’re planning to upgrade the ASPOSE.Imaging and ASPOSE.PDF from 21.8.0 to 22.12.0

It seems ContentMD5 hash value ( one of the property of Azure Blob File content) is different between the gray scale image created from version 22.12.0 and version 21.8.0 . The source file is same from which the gray scale images are created using version. 22.12.0 and version 21.8.0 .

because of ContentMD5 hash value change we’re facing some challenges.
Is there any logic change in version 22.12.0 for creating the Image that could be a reason behind different ContentMD5 hash value ?

2

@bikash.dutta1metlife.com , we are reviewing your request. You will be answered shortly!

3

Hello, @bikash.dutta1metlife.com ,
Both Aspose.Imaging and Aspose.PDF are being actively supported and developed, so the binary representation of output files may differ from version to version remaining its content similarity.
In case you are facing an issue with a certain file, you can share it here or create a privite thread so we can examine the issue and give you a feedback.
Hope this helps!

4

Thank you for your response. As you suggested, I created a private topic with additional details to discuss further.