Problem with edays after duration change

Aspose.Tasks Product Family
1

Hi

We are evaluating this tool before buying it, and have a Temporary License for Aspose.Tasks for .Net

As a proof of concept, I am trying to perform small modifications on a mpp of one of our customers.

The problem is that after I perform a task duration change, and save the file, I could notice that the plan duration goes to the double of the original time. I did this:

Task task = project.RootTask.Children.GetById(25);
task.Set(Tsk.Duration, project.GetDuration(12, TimeUnitType.Day));

The task # 25 is changed well, and now it has 12 days in duration. But the overall timing goes from 1000 days to 2000 days (the mpp has 700 tasks aprox).

Inspecting the other tasks I could find that the ones that had duration established in edays or emonths prior to the operation (and that are not involved in the duration change) are now set in a higher number of days or months,and no longer in edays or emonths.

Could you help me with this ?

Thank you in advance,

Best Regards

2

@fdesancho,

Thank you for contacting Aspose support team.

I have tried this scenario with some sample files but could not re-produce it. Could you please share the sample MPP file for our testing here? It will help us to observe the problem and provide assistance accordingly.

3

Hi, You can see it in this example. I took the Project1,mpp sample and change some tasks to edays.

image.png (22.6 KB)

After that, I executed this code:

public static void Run()
{
string dataDir = “C:\SomeDir”;
Project project = new Project(dataDir + “Before.mpp”);
Task task = project.RootTask.Children.GetById(3);
task.Set(Tsk.Duration, project.GetDuration(10, TimeUnitType.ElapsedDay));
project.Save(dataDir + “After.mpp”, SaveFileFormat.MPP);
}

And after that all tasks with edays duration changed to work days, and was multiplied by 3:

image.png (22.9 KB)

You can see it on the “before” and “after” mpp files on the zip attached

SampleProjects.zip (49.1 KB)

4

@fdesancho,

Thank you for providing sample data. This issue is observed and logged under Id:TASKSNET-2400 for further investigation. We will write back here once analysis is done and feedback is ready to share.