ExternalTask and IsSubproject always False ?!

I am currently evaluating this product to see if it is something my company would like to buy. I love how fast it can load large project files. It is by far the fastest product I have seen.

But the one thing that will prevent me from purchasing this product is that it seems to return invalid information. My company uses multiple linked project files and I need to be able to follow those links from Project to Project. For some reason your product always returns false for IsSubproject and ExternalTask. Maybe I am doing something wrong, but I have tested this at multiple times and cannot seem to figure out why it is always returning false.

Any help will be greatly appreciated and I would love to purchase this product. But if I cannot get the correct value for ExternalTask and IsSubproject then I will have to find a different solution

I have been using version 1.6.3

Hello,

Currently these properties implemented for XML format. We will check if it’s possible to add it also for MPP format in a short time. I will keep you posted.

Thanks for the extremely quick reply. I love your products. Some co-workers have been using your Aspose.Slides for some time now and it does so much more than PowerPoint itself. I am really impressed with the quality and efficiency your products have!

The issues you have found earlier (filed as 9913) have been fixed in this update.


This message was posted using Notification2Forum from Downloads module by aspose.notifier.

Thanks for updating the ExternalTask and IsSubproject to the latest Aspose.Task build. But your latest build has some problems. I have this pending post that is still a problem. Plus the latest build does not support ExtendedProperties which is a requirement for me.

<A href="https://forum.aspose.com/t/4596</A></P> <P>Is it possible for you to roll these changes you made into the 1.6.3 build you have?</P>

Hi,

Can you please provide the MS Project 2003 file that can not be opened with Aspose.Tasks for .NET 2.2.0.0.

Sorry that I cannot due to priorietary information in the project file. I did locate the source of the problem and created a post on my findings

Here is the link

The issues you have found earlier (filed as ) have been fixed in this Aspose.Words for JasperReports 18.3 update.