I am able to replicate the said issue with latest version of Aspose.BarCode for .NET v4.6.0. Therefore I have logged it in our bug tracking system for correction purposes. The ticket Id for your reference is BARCODENET-33175.
We will soon figure this out and will keep you posted with updates on this issue.
it’s been more than two month now that I’m waiting for a fix for my problem? As reading this kind of barcode worked very well in old versions I really don’t understand why this needs that much time to figure out and fix.
Could you please push that a little bit as I need it really urgent now!
First of all, please accept my sincere apologies for my delayed response.
I have discussed your reported issue with the development team and I have learned that the fix for this issue has been scheduled for the upcoming release of Aspose.BarCode for .NET v4.9.0. As you may know that we normally publish the latest release at the start of each month, so the v4.9.0 will be available for public use in first quarter of the next month (July).
Moreover, if we are able to fix the problem before the release date, we will be more than happy to inform you, and provide you a hotfix version for your testing.
I have just tested your sample with Aspose.BarCode for .NET v4.9.0, and I am glad to inform you that the latest assemblies can recognize the barcode symbol from your provided sample. I would request you to please give it a try at your end as well.
Regarding the resolution of the ticket, I have attached my comments to the ticket already associated with this thread. As soon as I receive more information, I will let you know here.