Hello,
I just obtained access to my DEV server and am trying to test aspose.word on it. All I have is a webform with a button that when clicked opens up a test document.
On the page load, when no aspose.word objects are accessed, I get an error that points to the filename of my webform.
Do I need a Deployment license to test this? Is there some type of test license to use in the code. Thanks!
If you post the error message here it could help me to answer better.
Aspose.Word will work without a license in evaluation mode. So as one of the steps towards resolution you can comment out the call to SetLicense and see if you can get this working.
Thanks Roman, the problem was I failed to copy the .dll to the bin root directory.
I have a question regarding the protection of different sections in a document. I saw a posting (https://forum.aspose.com/t/130161) that you might be working on adding this into aspose.word. What is the status of this? This feature would be really nice. Thanks!
We will try to get this feature delivered early in Februrary. Let me know if it is critical for you to have it earlier.
Hi roman, thanks for your quick replies. We are in the final stages of development of our application and would like this ability soon in order to fully test before moving to production. Thanks!
Awesome, Thanks!
Not sure if I should start a new thread or not so I’ll start out here first. I want to test out Aspose.Word and I’ve downloaded the eval copy. I’ve copied the DLL to the bin directory of the site I will using it on, added the reference to Aspose.WORD, added the IMPORTS ASPOSE.WORD and then added code to fill and open a word document that I created. When I run I get the following:
<<Exception Details: System.IO.FileNotFoundException: Could not find file “c:\inetpub\wwwroot\VenderClaims\Letters\VendorClaims.doc”.>>
Here is the stack info (not sure if it will help):
Stack Trace:
|
The point of error is this line of code:
Dim doc As Document = New Document(MapPath(“.”) + “\Letters\VendorClaims.doc”) |
Thanks.
Protection per section is supported, download the latest hotfix and see the Section.ProtectedForForms property.