I have analyzed the modified code and have observed the issue. It seems to be some regression issue and I am in contact with the development team to get the resolution for this. As soon as some feedback is received, I will inform you via this thread.
Please spare us little time and be patient for a while.
I was able to reproduce this issue at my end using the latest version of Aspose.Tasks for .NET 5.2.0 and have logged it in our bug tracking system under issue id: TASKS-33315. Development team will look into it and once we have any information regarding the resolution of this issue, we’ll update you here via this thread.
If you have any other query/inquiry regarding Aspose.Tasks, please feel free to post to us. We’ll try to assist you further as soon as possible.
I would like to share that if a task has to be started on specific day (task.Start), its ConstraintType should be MustStartOn. Similarly the task ConstraintDate should be equal to task Start date in order to have the appropriate dates in output file.
This change is required because MSP will use the constraint date for recalculation. If constraint dates are not set, MSP will consider any information it can like Project.StartDate, tasks.Early/late dates etc.
Please modify following segment of code in your sample and let us know your feedback.
// Create 10 new tasks for (int i = 0; i < 10; i++) { Aspose.Tasks.Task task = new Aspose.Tasks.Task(string.Format(“Task{0}”, i + 2)); task.Start = task1.Start;
//////////////////////////////////////////////// //Add these two lines task.ConstraintType = ConstraintType.MustStartOn; task.ConstraintDate = task.Start; ////////////////////////////////////////////////