I have a stakeholder with access to your products who would like to insert XML data in to an XFA form which has Adobe Reader Extensions applied, without violating the Reader Extensions. Is this possible with your tools? Thanks,
Hi,
Thanks for using our products and sorry for replying you late.
Aspose.Pdf for .NET supports the feature to import XML data into PDF form but I am afraid if the source PDF form has Adobe Readers Extension applied, it will be removed and I am afraid Aspose.Pdf for .NET might not be able to keep the Readers extension feature. Please note that Adobe LiveCycle Reader Extensions enables PDF forms designers to extend the use of Adobe Reader to allow for any advanced functionalities that they put into their forms, such as the ability to save or submit a PDF form. The ability to extend Adobe Reader this way is only possible using Adobe’s products.
Unfortunately, it is not possible for any non-Adobe owned product, to either create PDFs with extended usage rights or modify the extended usage rights on existing PDFs that were created with Adobe LiveCycle or Acrobat 9. In addition, if you modify a PDF – in any way, shape or form, with any none-Adobe product – that has had extended usage rights applied to it, it will invalidate the extended usage rights, resulting in an error message similar to the one listed below popping up when you open the document.
This document contained certain rights to enable special features in Adobe Reader. The document had been changed since it was created and these rights are no longer valid. Please contact the author for the original version of this document.
We apologize for your inconvenience.
Hi,
I have upgraded latest version of Aspose with the below link
http://www.aspose.com/community/files/51/.net-components/aspose.total-for-.net/entry228891.aspx
I have enabled Reader Extensions to the form using Acrobat X. I am referring Aspose.Total.Lic for all Aspose.barcode.dll and Aspose.Pdf. dll . I am experiencing the same issue as given in the above post.It is invalidating the reader extensions.
Before version i have Aspose.Pdf.Kit referring to Aspose.Pdf.kit.lic file. In the before version after applying the reader extensions, I have only the issue with displaying the barcode. For that i went to upgrade. So, Can i use the previous verion dll (Aspose.Pdf.Kit) for pdf and for barcode, can i use the newer version of Aspose.Barcode. I mean can i use the two different versions at the same time in same application.
Also can i refer to Aspose.Pdf.Kit.lic using older version of Aspose..Pdf.Kit.dll and Aspose.Total.Lic for newer version of Aspose.Barcode in the same application?
Thanks!
Hi Smita,
Thank you for the details.
sn733:
So, Can i use the previous version dll (Aspose.Pdf.Kit) for pdf and for barcode, can i use the newer version of Aspose.Barcode. I mean can i use the two different versions at the same time in the same application.
I am not really sure about your requirement. If you want to use two different versions of the same component (i.e. Aspose.Barcode for .NET) in one application, you will not be able to do that.
sn733:
Also can i refer to Aspose.Pdf.Kit.lic using the older version of Aspose.Pdf.Kit.dll and Aspose.Total.Lic for the newer version of Aspose.Barcode in the same application?
Yes, you can use your old Aspose.Pdf.Kit license with the older version of Aspose.Pdf.Kit and use your new license of Aspose.Total for the newest Aspose.Barcode in the same application. It will not cause any problem.
Please feel free to contact support in case you face any problem or have any other queries.
Thank You & Best Regards,
Hi,
Here I am trying to use Version 4.4 Aspose.Pdf.Kit dll referring the license file of Aspose.Pdf.Kit.lic which was the previous verison dll
and Version 4.5.0. Aspose.Barcode dll referring to the Aspose.Total.lic
I am getting the below error at Aspose.pdf.kit SetLicense method.
The license is not valid for this product. "
But it did'nt give me any error before i upgraded Aspose.barcode to the latest version
Can you please help me in this.
Thanks!
Hi
Smita,
Thanks for sharing the details.
As far as I have understood from problem description, you have been using older version of Aspose.Pdf.Kit and an older version of Aspose.Barcode and everything worked correctly, until you have upgraded Aspose.Barcode version. The problem seems to be quite strange because the upgrade of Aspose.Barcode product have started causing issues while setting license for Aspose.Pdf.Kit. Can you please try using the latest release version of Aspose.Pdf as it contains the combined features of Aspose.Pdf and legacy Aspose.Pdf.Kit for .NET. Please try using it and in case you still face any issue, please share the license file so that we can test the scenario at our end.
We are really sorry for your inconvenience.
Good morning, Nayyer
We have been able to resolve the many issues we have had with our forms and the ability to submit these forms to our application. However, there is one thing we are very confused about. I will try to outline the question as succinctly as possible:
We upgraded to the latest version of ASPOSE.TOTAL.
We used “Total” to submit our forms to the application. The forms submitted, but the submitted forms showed “Evaluation Copy” across the form ( Note: There was some other wording on the form along with “Evaluation Copy” and some of that wording mentioned the Aspose.Pdf.Kit license.)
So, we then installed the aspose.pdf.kit license, and, as a result, “Evaluation Copy” and all additional wording disappeared.
WHY did we have to install the aspose.pdf.kit license? It is our understanding that pdf.kit is part of ASPOSE.TOTAL.
This is very confusing to us. It may also be prudent to note that we have 4 ASPOSE licenses:
- aspose.pdf.kit
- aspose.words
- aspose.barcode
- aspose.total
Are we incorrect in our assumption that the ASPOSE.TOTAL license is the only one needed?
Thanks!
Deb Furlong
dfurlong@azcc.gov
Hello Deb,
Thanks for sharing the details.
Please note that Aspose.Total for .NET license should work with all Aspose.Total for .NET products and Aspose.Total for Java license should work with all Aspose.Total for Java products. Now concerning to your problem related to watermark on resultant PDF files when working with Aspose.Pdf.Kit, I think its occurring because license is not properly honoured by this product. Please note that since the release of Aspose.Pdf for .NET 6.0.0, all the features of Aspose.Pdf.Kit for .NET have been merged into Aspose.Pdf for .NET and all its classes and enumerations are present under Aspose.Pdf.Facades namespace present inside Aspose.Pdf for .NET.
So I would recommend you to please try using Aspose.Pdf for .NET and if Aspose.Total for .NET license is not expired, it should work with Aspose.Pdf for .NET. Please download the latest release version of Aspose.Pdf for .NET 6.6.0 and in case you face any problem, please feel free to contact. I would also suggest you to visit the following links for information on
Also checkout the following video tutorial on Migrating to new Merged Aspose.Pdf for .NET.
Last week, the developer on our project team finished up the Aspose research that you recommended in your last reply to me above. As it turns out, we are going to need to use the older Aspose.Pdf.Kit in order to get past the Adobe reader security (or whatever the hang-up is) that doesn’t allow us to update the XML and send it to the client PC.
We are getting an “error” message (I have attached the “error” message to this post) on a PC that doesn’t have Adobe Pro installed (Adobe Reader 9 and 10 is what we are testing with). We are getting the “error” message using the Aspose.Pdf.Facades DLL, which the documentation says replaces the Aspose.Pdf.Kit DLL in Aspose.Total. If we use the older Aspose.Pdf.Kit DLL, it works without a problem. The problem seems to be with the ImportXml method in the Form class. (The Aspose.PDF.Facades DLL does not technically replace the older Aspose.Pdf.Kit DLL since it does not work in the same manner.)
Our application prefills certain data elements on the form with XML data that is stored in our database. This is a necessary requirement in our application, both internally and on the public-facing website where our customers eFile their documents. The XML data that we are prefilling is the Customer Name and File number as it exists in our database from the customer’s previous filings. For all intents and purposes, we are not technically changing anything.
Please advise.
Good morning, Nayyer-
On Tuesday (2/7/12), I posted what you will find under the double lines, and in blue font, below. We are in need of knowing why the Aspose. PDF. Facades DLL, which, according to Aspose, replaces the older Aspose.Pdf.Kit DLL in Aspose.Total. We are finding that these two DLLs do not work in the same fashion at all. It is certainly not best practice for our installation to be on the latest version of the Aspose family of products, which in this case is Aspose.Total, but find ourselves having to use a DLL from a previous version of your product.
We have a couple of valid concerns with this approach:
- That a future version of Adobe Reader will render the older Aspose.pdf.kit DLL inoperable. This would not be a minor issue for us as our application would fail.
- That Aspose will discontinue support for the older Aspose.pdf.kit DLL.
Our team has come to the conclusion that the fact that the “pdf.facades” DLL and the “pdf.kit” DLL do not work in the same fashion is a bug that we are now officially requesting Aspose to fix/patch.
Please advise as to when you think this bug will be addressed so that we can replace our use of the older “pdf.kit” DLL with the “pdf.facades” DLL.
Thanks!
Last week, the developer on our project team finished up the Aspose research that you recommended in your last reply to me above. As it turns out we are going to need to use the older Aspose.Pdf.Kit in order to get past the Adobe reader security (or whatever the hang-up is) that doesn’t allow us to update the XML and send it to the client PC.
We are getting an “error” message (I have attached the “error” message to this post) on a PC that doesn’t have Adobe Pro installed (Adobe Reader 9 and 10 is what we are testing with). We are getting the “error” message using the Aspose.Pdf.Facades DLL, which the documentation says replaces the Aspose.Pdf.Kit DLL in Aspose.Total. If we use the older Aspose.Pdf.Kit DLL, it works without a problem. The problem seems to be with the ImportXml method in the Form class. (The Aspose.PDF.Facades DLL does not technically replace the older Aspose.Pdf.Kit DLL since it does not work in the same manner.)
Our application prefills certain data elements on the form with XML data that is stored in our database. This is a necessary requirement in our application, both internally and on the public-facing website where our customers eFile their documents. The XML data that we are prefilling is the Customer Name and File number as it exists in our database from the customer’s previous filings. For all intents and purposes, we are not technically changing anything.
Please advise and thank you
sn733:
1. That a future version of Adobe Reader will render the older Aspose.pdf.kit DLL inoperable. This would not be a minor issue for us as our application would fail.
Hello Deb,
Thanks for sharing the details and sorry for delay in response. From above statement, do you mean that latest versions of Adobe Reader might not be correctly displaying PDF documents generated with Aspose.Pdf.Kit for .NET ? Please share some details.
Since November 2011, we have stopped the production of new release versions and correction of issues in older code base of Aspose.Pdf.Kit for .NET. More along, we are encouraging our customers to migrate to the latest release version of Aspose.Pdf for .NET. Please note that if you are facing some problems while using the latest release version of Aspose.Pdf for .NET, we are honored to offer our services while correcting these issues. I would request you to please share the source PDF file and an XML file which can help us in replicating this issue at our end. We are really sorry for this inconvenience.2. That ASPOSE will discontinue support for the older Aspose.pdf.kit DLL.
Hi Nayyer-
I am going to copy your reply to this and then reply in a different color. The “copy” of your reply begins below the double-line below. What I’ve done is speak with my developer since he is the one who understands all of this the best.
My first question for him was: Is Aspose.Pdf.Kit for .NET the same thing as the Aspose. PDF. Facades DLL? He said that this is what you (Aspose) are saying, but that there are obvious differences, hence our original post from Tuesday (2/7/12).
Now onto your reply. You will find our responses in red.
sn733:
- That a future version of Adobe Reader will render the older Aspose.pdf.kit DLL inoperable. This would not be a minor issue for us as our application would fail.
Hello Deb,
Thanks for sharing the details and sorry for the delay in response. From your statement, do you mean that the latest versions of Adobe Reader might not correctly display PDF documents generated with Aspose.Pdf.Kit for .NET? Please share some details. I shared the message window (“error” message) that we get when we use Aspose.Pdf for .NET (facades namespace aka DLL). The Adobe Reader then disables the fillable portions of the PDF so that all the end user can do is print the form.
sn733:
- That Aspose will discontinue support for the older Aspose.pdf.kit DLL.
Since November 2011, we have stopped the production of new release versions and correction of issues in the older code base of Aspose.Pdf.Kit for .NET. Furthermore, we are encouraging our customers to migrate to the latest release version of Aspose.Pdf for .NET. This is exactly what we are trying to do. Please note that if you are facing some problems while using the latest release version of Aspose.Pdf for .NET, we are honored to offer our services while correcting these issues. I would request you to please share the source PDF file and an XML file which can help us in replicating this issue at our end. We are really sorry for this inconvenience.
Nayyer, what we have decided to do in an effort to “boil this down” is to provide to you one of our simpler forms. You will find the fillable PDF C006 attached. I have also attached the XML data for this form. Additionally, I have made a copy of the DocumentTemplateManager.cs and attached that.
The method in question is called GetPdfWithData and you will see some comments included in the method. We can start there, since there is a bunch of other stuff happening in between.
Basically, the user clicks the exam button in our application. The system retrieves the PDF template (a binary field in the database). The method “GetPdfWithData” returns the template with the data to the client. That’s the short and simple version.
Hello Deb,
Thanks for sharing the details and resource files.
I have tested the scenario using Aspose.Pdf.Facades namespace and have observed that same problems. However it does not seem to be occurring with Aspose.Pdf.Kit for .NET. For the sake of correction, I have logged this problem as PDFNEWNET-33290 in our issue tracking system. We will further look into the details of this problem and will keep you updated on the status of correction. We apologize for this inconvenience.
Good morning, Nayyer-
Have you an update on PDFNEWNET-33290?
Thanks!
Deb
Hi Deb,
Thanks for your patience.
Our development team is working hard to get this issue fixed but I am afraid its not yet completely resolved. However, I have requested the development team to share the ETA regarding its resolution. As soon as We get required information, We will be more than happy to update you with the status of correction. Please be patient and spare us little time.
We apologize for your inconvenience.
Thanks & Regards,
Hello Deb,
Thanks for your patience.
I am pleased to share that the issue reported earlier as PDFNEWNET-33290 is fixed and its hotfix will be included in next release version of Aspose.Pdf for .NET 6.9.0 which is expected to release early next month (April-2012). Please be patient and wait for the new release.
Your patience and comprehension is greatly appreciated in this regard.
The issues you have found earlier (filed as PDFNEWNET-33290) have been fixed in this update.
This message was posted using Notification2Forum from Downloads module by aspose.notifier.