How can I identify a ghost task as external task when linked between projects is broken? Aspose’s IsExternal task property is set to false, and ExternalTaskProject is set to null. When I open the file in MS Project, it provides me a dialog to fix, but even if I don't fix the link; ghost task is still shown as gray. Is there any other property that I can use to Identify ghost task besides what is mentioned above? I have attached a sample file with this post. Open del2.mpp
We have analyzed the requirement and found that IsExternal and ExternalTaskProject properties are working fine as they can be used to filter the external tasks and their respective project files. Following code filters all the external tasks and just prints the local tasks whether the linked project file is in-place or not. It does not effect whether link is broken or not to the external task during filtering tasks in the sample code.
Please give a try to the following code and let us know if it fulfills your requirement. Otherwise please elaborate the issue more and send us your compilable console application code which reproduces the issue.
//Create a project reader instance ProjectReader reader = new ProjectReader(); //Call read method of project reader object to get project object Project prj = reader.Read("TASK_418064\\del2.mpp"); //Declare ChildTasksCollector class object ChildTasksCollector collector = new ChildTasksCollector();
//Use TaskUtils to get all children tasks in RootTask TaskUtils.Apply(prj.RootTask, collector, 0); //Parse all the recursive children foreach (Task tsk in collector.Tasks) { if (!tsk.IsExternalTask) { Console.WriteLine(tsk.Id+ " : " + tsk.Name); } }
Thanks for your patience and we are sorry for any inconvenience caused to you in this regard.
Thanks for the quick reply! I did tested your code with new file and still seeing the ghost task. Task1 and Task2 should not show up. I have attached another files for you. Open 3513-3.
We have analyzed the sample MPP files and were successful in reproducing the issue here. We have passed the information to our development team and will update you here as soon as some feedback is received from the developers.
This issue is logged in our issue tracking system as TASKS-33226.
Please feel free to write us if you have any further query.