*Ugh*
Okay, with the new Aspose.Pdf.Kit 2.6.1.0 I pulled down today, I am STILL getting the following error...
Unable to cast object of type 'xeb116a323308e2f7.xacd3aca1cf90fb28' to type 'xeb116a323308e2f7.xe3033695b7f6d53d'.
Stack Track: at Aspose.Pdf.Kit.PdfFileEditor.Concatenate(Stream[] inputStreams, Stream outputStream)
at Fluor.DDMEmailRetrievalProcess.DominoAccess.ConcatinatePDFs()
at Fluor.DDMEmailRetrievalProcess.DominoAccess.ProcessDominoEmails()"
I don't get this on every document, but enough to make it an issue. This casting error was the original reason I pulled Aspose.Pdf.Kit 2.6.0.0 - because one of the Aspose.Pdf.Kit techs said it contained a fix for the casting error. As the story goes, after I installed 2.6.0.0 is when I started receiving the "Object reference not set to an instance of an object." error that started this thread. I don't seem to be getting THAT error any more, but I am back at square one with the casting error!
Please assist quickly...I like your products, but my client is becoming very skeptical of my recommendation to go with Aspose.Pdf.Kit
Regards,
Kyle Peters