We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

Release 7.0 and 7.1 not compatible

Hi,


I’ve got a project wich convert XML template to PDF (for billing).

The template working perfectly with de 7.0 release, but with 7.1 the generated file size is 0.
And it’s the same with de last release.(7.7)

What’s happened between v7.0 and v7.1 ?


Hi Prezut,


Thanks for your inquiry. Could you please share your sample XML template here? So we will test it at our end and provide you information accordingly.

Sorry for the inconvenience faced.

Best Regards,

Unfortunately,


Due to confidentiality reasons I can’t give you my samples. But I’m working on a way to reproduce the issue.

I will keep you notified as soon as possible.

Thx

Hi Prezut,

Thanks for your feedback. As soon as we receive your sample, we will test it and provide you the details.

In reference to confidentiality issue, if it's convenient for you then you can share your sample and mark your post as private, check box option is available in bottom of reply page. So only the thread initiator and Aspose staff will have access to the post and attachments.

Best Regards,

Hi,

So, here are my samples.

You’ll find :
- 2 Classes (Resume.cs and Tool.cs)
- Xml Template (Template4Aspose.xml)
- Result with release 7.0.0 (r7_0.pdf) (.net framwork 4.0)
- Result with release 7.7.0 (r7_7.pdf) (.net framwork 4.0)

To start i used :

var license = new Aspose.Pdf.License();
license.SetLicense(“Aspose.Total.lic”);
var pdf = new Pdf { IsTruetypeFontMapCached = false };
pdf.BindXML(“Template4Aspose.xml”, null);

AsposeTests.Resume.Bind(pdf);

pdf.Save(“Template4Aspose.pdf”);

So, You’ll find 2 issues :

First, the border not appearing with v7.7.

Second, the generate file size is null.
I observe that :
There is two rows in my template : ID = HORS_FORFAIT_TITLE and ID = AU_DELA_TITLE

When you switch those two ID, that fix the size issue (if AU_DELA_TITLE first => pb)





Hi Prezut,


Thanks for the additional information. I’ve managed to reproduce the issue on my side and logged the
issue in our bug tracking system for further investigation and resolution, the
issue ID is PDFNEWNET-34901. I’ve also linked your request to this issue and
you will be notified as soon as it is resolved via this thread.

Sorry for the inconvenience faced.

Best Regards,