Free Support Forum - aspose.com

PDF.Kit 5.9

Hi,

we have recently purchased and downloaded the latest Apose 7.4, especially to solve an issue that we had with Aspose.PDF.Kit v5.6 ~one year ago.
At this time, you had delivered 5.9 that fixed the issue.
Now unfortunately 7.4 seems to have some know issue (PDFNEWNET-34526) but additionally we would like to avoid changing our code because otherwise this will mean that our clients will have to apply the latest version of our software.
That is why we would like to get this 5.9 DLLs (same requirement as in http://www.aspose.com/community/forums/432469/working-with-aspose.pdf-ver-7.4-and-document-privileges-issue/showthread.aspx#432469)

Thanks,
Jerome

jgauthier@cpaglobal.com:
,
we have recently purchased and downloaded the latest Apose 7.4, especially to solve an issue that we had with Aspose.PDF.Kit v5.6 ~one year ago.
At this time, you had delivered 5.9 that fixed the issue.
Now unfortunately 7.4 seems to have some know issue (PDFNEWNET-34526)
Hi Jerome,

I have tested the scenario using Aspose.Pdf for .NET 7.5.0 with a little variation in code (as suggested earlier by Nausherwan). The code should be

[C#]

DataSet ds = new DataSet();<o:p></o:p>

ds.ReadXml(@"c:\pdftest\DataSetXml.xml");

XmlDataDocument dataXmlDoc = new XmlDataDocument(ds);

XslTransform xslTran = new XslTransform();

//FileStream outputXml = new FileStream();

string tempFile = "";

tempFile = @"c:\pdftest\out.xml";

FileStream outputXml = new FileStream(tempFile, FileMode.Create);

xslTran.Load(@"c:\pdftest\PTO-SB-14+XSLT.xml");

xslTran.Transform(dataXmlDoc, null, outputXml);

ImportXml(@"c:\pdftest\PTO-SB-14+v11-08 (1) - Copy.pdf", outputXml);

private void ImportXml(string templatePdf, FileStream xml)

{

Aspose.Pdf.Facades.Form form = new Aspose.Pdf.Facades.Form();

//form.DestFileName = destFileName;

FileStream fs = new FileStream(templatePdf, FileMode.Open, FileAccess.ReadWrite);

form.BindPdf(fs);

xml.Seek(0, SeekOrigin.Begin);

form.ImportXml(xml);

form.Save(fs);

fs.Close();

}


See the attached PTO-SB-14+v11-08_7_5_0.pdf output document.
jgauthier@cpaglobal.com:
but additionally we would like to avoid changing our code because otherwise this will mean that our clients will have to apply the latest version of our software.
Did you try using the latest release version or product release versions of Merged API of Aspose.Pdf for .NET. Please note that we encourage our customers to use the latest release versions because all the issues are fixed and new features are provided in latest release versions.

The issues you have found earlier (filed as PDFNEWNET-34526) have been fixed in Aspose.Pdf for .NET 7.6.0.


This message was posted using Notification2Forum from Downloads module by aspose.notifier.

Hi Shahbaz,

We downloaded the latest version of Aspose.PDF (ver 7.6) and tried your proposed solution. Though we did not see any exceptions or errors, the window pops-up to stream the PDF but nothing gets displayed. we see a blank screen.

We navigated to the TEMP folder where the temporary PDF file gets created and tried opening that. The issue with "not allowing to fill fields" seems to be resolved there.

Could you tell us the reason why the PDF does not stream or open in the browser? Here is the snippet of the code that we use as per your proposed solution:

private void ImportXml(string templatePdf, FileStream xml, string destFileName)
{


Aspose.Pdf.License pdfLicense = new Aspose.Pdf.License();
pdfLicense.SetLicense(HttpContext.Current.Server.MapPath(HttpContext.Current.Request.ApplicationPath + "/Aspose.Total.lic"));
Aspose.Pdf.Facades.Form form = new Aspose.Pdf.Facades.Form();

//form.DestFileName = destFileName;

FileStream fs = new FileStream(templatePdf, FileMode.Open, FileAccess.ReadWrite);
form.BindPdf(fs);
xml.Seek(0, SeekOrigin.Begin);
form.ImportXml(xml);
form.Save(fs);
fs.Close();

}

Hi Jerome,


I have tested the scenario using Aspose.Pdf for .NET 7.6.0 and as per my observations, the resultant PDF is properly being generated. I have used the resources shared over 426939. If you are still noticing the same issue, please share some sample project so that we can again test the scenario. We are sorry for this inconvenience.