"File damaged and could not be repaired" .net2 dll

I've recently updated our development server by installing .NET 4.0.

Since then we have noticed that our PDFs across all our test urls now fail to open, with the error "The file is damaged and could not be repaired. Local\EWH-5180-0".

We're running Server 2003 and DynamicPDF Generator 6. The same code works fine on our production server where .NET 4 is not installed. All the urls were running under the correct .net 2 process in a separate app pool.

The code was referencing the .NET 2 dll. Upgrading the affected project's DynamicPDF dll to the .net3.5 build cured the issue, but we then had to double check that this was deployable on our production server.

Just wondered if this was a known issue and if there's a logical explanation for why this error occurs?

Hello,

Installing the v4 .NET framework will not affect the creation of PDF using our DynamicPDF for .NET API. Please send over the following details to our support team so that they can do some testing on their end.

1.Damaged output PDF.
2.Version of the Reader used to view the PDF.
3.Sample code used.
4.Exact version and build number of the DynamicPDF DLL file. You can get this information using Visual Studio References properties (Description) of the DynamicPDF DLL.

Thanks,
ceTe Software Support Team.

Hello,

The latest build of v6 resolves this issue. It can be downloaded from the customer area.

Thanks,
ceTe Software Support Team.