How to check valid Image using stream?

[cyginfo]

I’m trying to validate image file using below method:

     if (System.IO.File.Exists("D:\\architecture.png"))
                    {
                        using (var streams = new FileStream("D:\\architecture.png",FileMode.Open))
                        {
                            bIsValid = Aspose.Imaging.Image.CanLoad(streams);
                        }
                    }

CanLoad method throws error:
System.ArgumentOutOfRangeException: Non-negative number required. Parameter name: count

How to check valid Image file using stream?

PS: I referred below links but solution found.

https://apireference.aspose.com/net/imaging/aspose.imaging/image/methods/canload

System.ArgumentOutOfRangeException: Non-negative number required. Parameter name: count

Hello, Just finished examining the demos and decided to try to open a Word form but alas. I get the above error. I can open simple word files (plain text) but the file that I have to open is seriously formatted. I searched previous posts and the same problem was encounrered before and was fixed with a hotfix for Word.1.etc . As I'm using 3.x I'm not sure a previous hotfix can help me. Waiting for any ideas, nimloth

architecture.png (91.8 KB)

[mudassir.fayyaz]

@cyginfo,

I have observed the issue shared by you and request you to please provide the source file reproducing the issue. Please also try setting the stream position to 0 as well before checking.

[cyginfo]

I’ve attached and updated my query. Although, I’m facing same issue in image file format(.jpg,.png,.bmp)

[mudassir.fayyaz]

@cyginfo,

I have worked with your file using Aspose.Imaging for .NET 19.12 and there is no issue while verifying the stream using Aspose.Imaging. Can you please try using shared project.

TestImaging.zip (186.0 KB)

[cyginfo]

Thank you. But we are using Aspose.Imaging 19.1 version.

Is there any way to validate Image stream without having to update version?

[mudassir.fayyaz]

@cyginfo,

I like to share that we can only log issue if it is getting reproduced using latest version. In your case, I suggest you to please try using latest Aspose.Imaging for .NET 19.12 on your end.