Does the Tasks API allow for opening password-protected project files? I do not see any mention of it in the API documentation, and as expected, opening of such a MPP/2003 file fails.
This issue has been logged into our issue tracking system as <!–[if gte mso 9]>
<m:mathFont m:val=“Cambria Math”/>
<![endif]–><!–[if gte mso 10]>
<![endif]–><span style=“font-size: 13.5pt; font-family: “Arial”,“sans-serif”;”>TASKS-27053. We will keep you updated on this issue in this thread. We are extremely sorry for the inconvenience.
Please feel free to contact us in case you have further comments or questions.
Is this issue (TASKS-27053) is fixed or inform me the estimated time to fix this issue. I am using Aspose.Tasks.dll for .net version 188.8.131.52 to read the project file. I need to add support for password protected project files in my application.
This issue is not fixed yet and it is not in our nearest plan however we will update you once our developers have a concrete plan about this feature. Sorry for the inconvenience.
It has been over 8 months since this thread was updated. Can you please confirm when we might be seeing support for password protected documents?
This issue was delayed because our developers were working on MPP write feature. I have asked the developers to analyze this issue and share the ETA. We will share the ETA once our developers analyze this issue. Sorry for the inconvenience.
Completing 'MPP write support' feature is the top priority at the moment due to which 'support for password protected documents' feature has been shifted to Q4' 2012. Please let us know if you need this feature urgently. We can make changes in the plan for show-stopper features.
Well, of course I’d like the fix as soon as possible! However there is a workaround in place so Q4 will be ok. please don’t let it slip beyond that though.
Thanks a lot for your cooperation. This issue has been added to our Q4 plans and will be fixed accordingly.
The issues you have found earlier (filed as TASKS-33368) have been fixed in this update.
This message was posted using Notification2Forum from Downloads module by Aspose Notifier.
The issues you have found earlier (filed as ) have been fixed in this Aspose.Words for JasperReports 18.3 update.