I am currently evaluating the Aspose.Project. So far, looks great and promising.
I have a question: Is it possible to access custom document properties of a mpp file? If not, are there plans for this?
Thanks!
Dan
I am currently evaluating the Aspose.Project. So far, looks great and promising.
I have a question: Is it possible to access custom document properties of a mpp file? If not, are there plans for this?
Thanks!
Dan
Dear Dan,
We have planes to add such feature in Aspose.PowerPoint.
After that will be implemented we will add it also to Aspose.Project.
Thanks for the reply!
I am happy to hear that. What is the timeline for such a feature?
Thanks,
Dan
I think end of October or beginning of November.
any update on the status of custom document properties?
Thanks,
dan
Hi!
Is support for custom properties implemented already ?
If yes, could you please, provide an example ?
Hi Olexandr,
Hi Olexandr,
Sorry for misunderstanding.
From your previous requests I can see now that the question was about project’s custom properties (see screenshot attached).
Unfortunately, the feature is not supported by Aspose.Tasks now.
A new issue ‘Reading project’s custom properties values from MPP 2003/2007 files.’ with ID=14745 has been created and linked to this forum thread. The issue resolving deadline is the end of April.
Hi,
You are right, that’s what I mean.
Thank you for the information!
The issues you have found earlier (filed as 14745) have been fixed in this update.
Hi Olexandr,
ProjectReader reader = new ProjectReader();
Project project;
project = reader.Read("..\\..\\..\\testdata\\ProjectSummary\\DocSummaryInfo2007.mpp");
Hashtable customProperties = project.CustomProperties;
Assert.AreEqual(customProperties["MyText"], "MyTextValue");
Assert.AreEqual(customProperties["MyDate"], new DateTime(2010, 4, 21));
Assert.AreEqual(customProperties["MyNumber"], 100);
Assert.AreEqual(customProperties["MyFlag"], true);
The hashtable contains application specific and user
defined project properties.
The issues you have found earlier (filed as ) have been fixed in this Aspose.Words for JasperReports 18.3 update.