Handling Critical and Effort-Driven Tasks

Microsoft Project recognized a number of different types of tasks. Tasks with no duration, for example, are considered milestones by default. Critical tasks make up the critical path, one or a series of tasks that, ultimately, determines how long a project will take.

Working with Critical and Effort-Driven Tasks

The Tsk class exposes the IsCritical and IsEffortDriven properties to handle critical and effort driven tasks:

• IsCritical sets or gets whether a task is critical (boolean).
• IsEffortDriven: sets or gets whether a task is effort-driven (boolean).

Critical and Effort-driven Tasks Microsoft Project

To check whether a task is critical or effort-driven in Microsoft Project one need to double-click a task in the Task Entry form:

Getting Critical and Effort-Driven Tasks

The following code examples show how to get information about whether a task is critical or effort-driven.

Project project = new Project("New Project.mpp");

// Create a ChildTasksCollector instance
ChildTasksCollector collector = new ChildTasksCollector();

// Collect all the tasks from RootTask using TaskUtils
TaskUtils.Apply(project.RootTask, collector, 0);

// Parse through all the collected tasks
foreach (Task task in collector.Tasks)
{
    string strED = task.Get(Tsk.IsEffortDriven) ? "EffortDriven" : "Non-EffortDriven";
    string strCrit = task.Get(Tsk.IsCritical) ? "Critical" : "Non-Critical";
    Console.WriteLine(task.Get(Tsk.Name) + " : " + strED);
    Console.WriteLine(task.Get(Tsk.Name) + " : " + strCrit);
}