public MemoryStream InsertPages(MemoryStream inputFile, int index, MemoryStream pageStream) { MemoryStream retVal = new MemoryStream(); if (inputFile != null) { Aspose.Pdf.Document pdfDocument = new Aspose.Pdf.Document(inputFile); Page newPage = pdfDocument.Pages.Insert(index); PageCollection pageCollection = pdfDocument.Pages; double pdfPageWith, pdfPageHeight; double lly, llx, urx, ury; if (pageCollection.Count != 0) { pdfPageWith = newPage.Rect.Width; pdfPageHeight = newPage.Rect.Height; lly = newPage.Rect.LLY; llx = newPage.Rect.LLX; ury = newPage.Rect.URY; urx = newPage.Rect.URX; newPage.SetPageSize(pdfPageWith, pdfPageHeight); Aspose.Pdf.Facades.PdfFileMend fileMend = new Aspose.Pdf.Facades.PdfFileMend(pdfDocument); using (pageStream) { float pdfPageHeightLLY = (float)lly; float pdfPageWidthLLX = (float)llx; float pdfPageHeightURY = (float)ury; float pdfPageWidthURX = (float)urx; if (pageStream != null) { fileMend.AddImage(pageStream, index, pdfPageWidthLLX, pdfPageHeightLLY, pdfPageWidthURX, pdfPageHeightURY); } } pdfDocument.Save(retVal); fileMend.Close(); } return retVal; }
"If we were to setup a HTML table with CSS styles inline for widths using pixels as a unit of measure would the output render ok? If so do you know how it converts pixels into a unit of measure for printing>? I’m assuming via page size/paper size maybe?"
Hello every one,
I can prove the issue is on Aspose side with a web test process we wrote, with this you can reproduce the issue when generating PDF, i.e. initial attempt is lengthy.
The way to apply this web process: deploy it in IIS, click Export PDF on WebForm1.aspx, it may take about 1 minute in first try, subsequent exporting would be faster. If you don't use IsHtmlTagSupported property,there is no this problem.
Problem is each time after IIS restarted or reached Idle Time-out(minutes) in IIS, the issue reoccurs! Deploying this web process in IIS can help reproduce the issue, only debugging it won't help.So I think this problem and used in the web project has a lot to do.