Oh I see that makes sense.
Perhaps the problem is that Im not changing any milestone duration, just trying to shift the milestones all by a number of days, simply by moving the first milestone.
string newProject = “SourceProject.mpp”;<o:p></o:p>
Project project = new Project(newProject);
string testFile = "OutputMSP.mpp";
//Declare ChildTasksCollector class object
ChildTasksCollector collector = new ChildTasksCollector();
//Use TaskUtils to get all children tasks in RootTask
TaskUtils.Apply(project.RootTask, collector, 0);
Task task1 = project.GetTaskById(1);
task1.Start = new DateTime(2013, 07, 02, 8, 0, 0);
project.RootTask.Start = task1.Start;
//Save the Project
In case the problem still exists, please provide us a sample file so as we can assist you further as soon as possible.
This is the difference. Not sure I understand why the second two would be needd if the task structure hasn’t changed.
But I will try this.
Also HERE has no link.
Well now as before if I recalculate the task it works, but on one MPP it doesn’t. Althought it passes the verify check.
Please explain carefully what they do.
I suppose you have the ZIP already. I realized it still contains personal data, so I had to remove it. If you dont have rthe zip then I can put it up again briefly. This thread is also now marked as privae.
firstname.lastname@example.org:1. There is an orphan milestone that will cause the application to fail on tasks.recalculate(tsk). It will loop in aspose tasks, run out of memory and crash the application. I am guessing this will happen on recalculating any task that has no dependencies. I now check for this and warn the user to correct the MPP, so it is not urgent.
email@example.com:2. You see task 15 (j) has a number of predecessors. Recalculate the project START end date using the mpp and everything works perfectly. Eg shift it forward by some days. But using Aspose the predecessor rules are not honored and the task J is not calculated correctly. Eg the total extent of the project is reduced.
Sorry dis not explain clearly. You already have it. There is an inactive task in bad.mpp, just make it active.
Sorry did not explain clearly. You already have it. There is an inactive task in bad.mpp, just make it active.
for point 2, is there a workaround? If we cannot resolve this quickly we will have to forget Aspose Taks as being too unreliable. I will have to review it with the customer later today and tell them the bad news.