[MarmiteX1]

Hi,

I am procesing some product images in my console app and some the images seem to be corrupted.

I firstly check if the file exists

try 
{
if(File.Exists(filepath)==true)
{
  //process it
   GenerateImage(filePath);
  //notify user using my own email utility class
  //EmailUtil.SendEmail(userId)

}
}
catch(.......)
{
 Console.WriteLine(ex.message);
}

I get an exception:

"Parameter is not valid".

When i go to view the image in my ProductImages folder and select the image that is causing the issue I get the following:

"Windows Photo Viewer cannot open this file since the file is empty."

Is there an inbuilt functionality available in the .NET framework by any chance to not to process corrupted images? Or do I have to ensure I dont deal with corrupted images in the first place?

Any thoughts on the above would be much appreciated.

Thanks in advance

This post has been edited by MarmiteX1: 13 January 2011 - 06:03 AM

[Fungle]

From what I gather, The parameter is not valid error could be referencing the actual path itself instead of the destination directory.

Also if the photo viewer claims the file is empty then have you tried using a different image? or checking that the image is in the project directory in the first place?

[MarmiteX1]

Fungle, on 13 January 2011 - 05:15 AM, said:

From what I gather, The parameter is not valid error could be referencing the actual path itself instead of the destination directory.

Also if the photo viewer claims the file is empty then have you tried using a different image? or checking that the image is in the project directory in the first place?

I pasted the filepath in windows explorer and it can find the file.

I've tried a different image and it works. I think the issue lies with the image itself don't you think?

Thanks,

[Fungle]

Yeah it seems that somehow your original image has turned into a shell of what it once was

Must of been the image then.

[tlhIn`toq]

You could also check the size of the file. If it is 0k for example you know it's fraked.
You could try loading the image as a byte array. If that fails you know it's fraked.
You simply can't trust Image.FromFile(stringPathToFile); from the framework because it sucks.