We’re using Aspose.Words 11.3.0.0 under .NET 3.5 to convert Word documents to PDFs for display on ASP.NET websites.
We’ve hit a problem where a 240Kb .doc file is causing IIS to timeout on a call to Aspose.Words.Document.Save(stream As System.IO.Stream, saveFormat As Aspose.Words.SaveFormat)
(It’s purely text, 30 pages, there are no images that I’m aware of.)
It contains masses of personal information (it’s a CV that’s been submitted to one of our sites) and therefore I am not particularly happy to submit it to you for examination.
Do you have any sort of privacy policy that would allow us to submit this information to you, with the knowledge that it is secure and will not be used for any other purpose than discover why Aspose.Words is failing?
EDIT:
I have downloaded the 14.1.0 DLL to test with, and that has “worked” on the document.
However, that is not a true test, as the “evaluation” mode only converts the first 5 pages and places the evaluation warning banner. There is no way of knowing if the document would work with the fully licensed version of the DLL.
Cheers,
Tom
Hi Tom,
Hi Awais,
Thanks for your response, which basically boils down to this…
"We’re not willing to fix the issue that exists in the software you have already paid us a LOT of money for.
Instead, if you want a WORKING version of the software, please pay us a LOT MORE money."
The question is, after I paid you lots more money - will the new version even work?
And will you actually answer the question I original asked, which is what you privacy policy is - as the document is a CV of a client, and therefore contains huge quantities of sensitive information.
And therefore I will definitely NOT attach it to this public forum. Can you please give me an email address that I can sent to?
Cheers,
Tom
Hi Tom,
Do you actually read anything I say?
Did you test it against v11.3 to prove that there is a problem with that version of your component?
Unless you do that, how can you justify saying that we need to upgrade?
Yes, we could upgrade (FOR A LOT OF MONEY) to fix a problem that is in the software (THAT WE PAID A LOT OF MONEY FOR) to find that it still doesn’t work in our system, because of something unrelated.
Unless it’s not obvious from what I’m saying, I’m not impressed that we need to pay you money to fix a fault that is stopping our system from working correctly.
Hi Tom,