Hi…
I’m evaluating a trial version of Aspose.Tasks and am having trouble with the calculation of values.
I have as simple application written in VB.NET where I load in a simple test project, then write the tasks names, durations, start, and finish times to the console output. This works fine, and the values I get match the values in Microsoft Project.
Next, I change some of the duration values, and the write out the updated values of these same items again. Now my results are very different from what project gives.
I’ve attached a .zip file with my full project. The testing .mpp file isin the \bin\debug directory (which is where I’m running the code from.) All the dates are within the year 2000 to meet the requirements of running a trial version.
The output of the console looks like this:
Aspose.Tasks Test
Task Information Before Changes:
Name Duration Start Finish
Design 60 days 1/3/2000 8:00:00 AM 3/24/2000 5:00:00 PM
Construction 120 days 3/27/2000 8:00:00 AM 9/8/2000 5:00:00 PM
Cleanup 30 days 9/11/2000 8:00:00 AM 10/20/2000 5:00:00 PM
Project Complete 0 days 10/20/2000 5:00:00 PM 10/20/2000 5:00:00 PM
Task Information After Changes:
Name Duration Start Finish
Design 57 days 1/3/2000 8:00:00 AM 3/21/2000 5:00:00 PM
Construction 123 days 3/27/2000 8:00:00 AM 9/13/2000 5:00:00 PM
Cleanup 38 days 9/11/2000 8:00:00 AM 11/1/2000 5:00:00 PM
Project Complete 0 days 10/20/2000 5:00:00 PM 10/20/2000 5:00:00 PM
Now compare:
If open the test file in MS Project, and change the first three task durations to be 57, 123, and 38 days, respectively, and then force a recalc (if necessary) you’ll get some different results than what are shown above. For example, look at the “Construction” task, in MS Project it says 9/8/2000 whereas the console app returns 9/13/2000.
What am I doing wrong?
Thanks,
Erik
I applied for a temporary license and when I used that the problem went away. There must have been some subtle additional limitation of the non-licensed evaluation version that was causing the problem…
Hi Erik,
Thank you for writing to us. I have also tried this issue using a valid license and observed that issue is no more there. You are right, that there is some additional limitation for the non-licensed evaluation version. You may please use temporary license or a valid license in your application for further testing.
Please feel free to write us back if you have any other query in this regard.