PDFsharp & MigraDoc Foundation

I've got a very strange issue here - we use PDFsharp 1.31 as part of a C# application that generates PDFs, which are then made available to download on the web. We've had a number of customers report that when they open the PDFs they appear entirely blank, however if we open the same thing it looks fine.

Even more strange, if we send them the file as an e-mail attachment it also opens fine for them, suggesting it is something to do with being opened 'in browser'. We've asked a few times for people to send us the blank PDFs they have, and they do indeed appear blank to me in various versions of Reader etc, however judging by the headers (the PDF version jumps from 1.4 to 1.6) these have been modified by Acrobat (so they've presumably used the 'Save a Copy' button or whatever).

I'm trying to collect information as to what version of Acrobat people are using when this happens, however this is proving tricky as once people have a PDF that works for them they tend to go quiet and not care any more.

Has anybody seen anything similar, and if so any suggestions for things we could try that might fix it?

Further information if useful - the PDFs are A4, created by taking a single page A4 template PDF, and placing some text and images over this.

Don't know if it's the same problem but I uninstall and reinstall Adobe Acrobat (last version 10.1.3) and it open in Firefox without problem, but have always a blank page in IE8:?:... I have to refresh (not just F5) to see the PDF.

Maybe it's an Adobe version problem...

Good luck

Thanks for the info - I managed to reproduce it, at which point it turned out to only affect IE8. Further investigation revealed it was a separate part of our code that fixed up some other issue in IE8 that was corrupting the PDF - doh!

If I understans, some code somewhere corrupt IE8 PDF... Thanks, and if its the same for me, wish me luck.

In my case it was some code unique to my application - it was there to resolve another IE8 issue we'd had and unfortunately it seems it kicked in on the binary data going out in the PDF and mangled it. It had nothing to do with PDFsharp or IE8 itself so I don't think you're likely to hit the same unfortunately...