Free Support Forum -

Unable to read ExtendedAttributes in Aspose.Tasks.Task

Hi all,

My name is Grigory. I am .net developer. I have developed the project that is importing data from mpp file into database using knowledge file.
I had received an MPP file in which is added extended columns, like Cost1, Text1, etc.
I see the ExtendedAttributes collection in the Aspose.Tasks.Project object , but I can't read the extended attributes data from task, because the task.ExtendedAttribute collection return 0 count.
The fields like Cost1, Text1 is not presented as Property in Aspose.Tasks.Task class.
Anyone, know how I can read data ?

In the knowledge file i have defined the property names that is used in mpp file, example: Name, Cost, Start, Finish etc.
I am reading data from tasks recursively like below:

public object getCellValue(string name, Task task)
PropertyInfo pi = task.GetType().GetProperty(name);
object value = pi.GetValue(task, null);
return value;

Thanks in advance.


Can you please attach a sample for analysis? We have fixed a couple of ExtendedAttributes related issues for our upcoming release. If you can provide a sample, we will be able to test this sample with our upcoming release too.

Best Regards,

Thanks for kindly fast answer Muhammad,

Please find attached the file.
Please see below the Extended fields:
Disbursement (Cost2)
Code (Text2)

The file is saved in MPP 2003 format. When I save the file in 2010 format the extended attributes is visible for the program. I am using Aspose.Tasks for .NET 3.7.0

Thanks in advance


This issue has already been logged into our issue tracking system as
<!–[if gte mso 9]>
<m:mathFont m:val=“Cambria Math”/>
<m:brkBin m:val=“before”/>
<m:brkBinSub m:val="–"/>
<m:smallFrac m:val=“off”/>
<m:lMargin m:val=“0”/>
<m:rMargin m:val=“0”/>
<m:defJc m:val=“centerGroup”/>
<m:wrapIndent m:val=“1440”/>
<m:intLim m:val=“subSup”/>
<m:naryLim m:val=“undOvr”/>
<![endif]–><!–[if gte mso 10]>

/* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:Arial; mso-bidi-theme-font:minor-bidi;}

<![endif]–><span style=“font-size:13.5pt;font-family:“Arial”,“sans-serif”;
and it has been fixed but it will be included in the coming release due in this month. We will notify you once this release is published.

Please feel free to contact us in case you have further comments or questions.

Best Regards,

The issues you have found earlier (filed as 26733) 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.