Our solution, which also uses the product ASPOSE PDF for .NET should be deployed in production in August. We have big problems to explain our customer unprofessional way that company ASPOSE have to fix this issue. This problem has been reported in July. The problem was caused because you refused to sell us a license for PDF Kit, because the functionality was embedded into the PDF for .NET. We have tested PDF Kit and everything was fine, the description for PDF for.NET noted that the functionality of generating images from PDF files will be maintained.
I have tested the above specified scenarios using Aspose.Pdf for .NET 6.1.0 and I am able to notice the same issues. For the sake of correction, I have logged these issues as PDFNEWNET-30309 in our issue tracking system. However concerning to missing properties, as I have stated in other forum thread,these properties are supplementary and not mandatory when converting PDF file into TIFF image.
For the time being, as a workaround you may continue using Aspose.Pdf.Kit for .NET to generate correct output. Please generate the Temporary License for Aspose.Total for .NET and use it with Aspose.Pdf.Kit for .NET. We will try our level best to fix above specified issues ASAP and will get back to you soon. We apologize for your inconvenience.
Our solution, which also uses the product ASPOSE PDF for .NET should be deployed in production in August. We have big problems to explain our customer unprofessional way that company ASPOSE have to fix this issue. This problem has been reported in July. The problem was caused because you refused to sell us a license for PDF Kit, because the functionality was embedded into the PDF for .NET. We have tested PDF Kit and everything was fine, the description for PDF for.NET noted that the functionality of generating images from PDF files will be maintained.