Both Project.net and Microsoft Project allow the scheduled dates of a task to be constrained so its starts or finishes no later than, no earlier than, or on a specific date.
Tasks in Project.net have constraints that require that the start and/or finish date of a task be no later than, no earlier than, or on a specific date. Constraints are not enforced at all for manual tasks, and for automatic tasks, they are only enforced when the workplan is rescheduled. This article talks about how constraints can be set, and how they can be visually identified in a workplan.
Project.net has two kinds of leaf tasks – manual tasks and automatic tasks. Manual tasks are manually scheduled. They should be used when you want to explicitly set a task's start and finish dates and not allow it to be changed automatically by the scheduler based on changes to other tasks. However, as in Microsoft Project, the start and finish dates and the duration are tied to one another. This article discusses how the duration and scheduled start and finish dates of manual tasks are tied to one another, and how manual scheduling is enabled.
Project.net has two kinds of leaf tasks – manual and automatic. Automatic tasks (also called calculated tasks) are automatically scheduled. They should be used when you want the project.net workplan scheduler to automatically set the start and finish dates of a task, based upon its work and duration, its constraints, and its dependencies on other tasks. In this article, we're going to talk about how automatic tasks are scheduled by the scheduler.
Work, Duration & Calculation Types
Project.net, like Microsoft Project, supports 3 calculation types (also called task types) – fixed-work, fixed-duration, and fixed-units. In this article, we're going to talk about how they affect work and duration, and which one you should use.