TaskLinkType
Which end of the predecessor a link waits for, and which end of the successor it holds: the four dependency types of the critical-path method.
public enum TaskLinkType
Remarks
Planners write them as two letters – FS, SS, FF and SF – and so does the Gantt chart's
Predecessors column (3SS+1); ProjectScheduler.Code gives the code for a type.
Any lag (TaskLink.Lag) is added to the date the link waits for.
See also
Members at a glance
| Members | |
|---|---|
FinishToFinish | The successor cannot finish until the predecessor has finished: "documentation finishes when development does". Written FF. |
FinishToStart | The successor starts once the predecessor has finished: "test after build". By far the most common, and the default. Written FS. |
StartToFinish | The successor cannot finish until the predecessor has started: "the old system runs until the new one starts". Rare, but some plans need it. Written SF. |
StartToStart | The successor starts once the predecessor has started, so the two can run side by side: "start the API two days into the wireframes". Written SS. |
Members
FinishToFinish
The successor cannot finish until the predecessor has finished: "documentation finishes when development does". Written FF.
FinishToStart
The successor starts once the predecessor has finished: "test after build". By far the most common, and the default. Written FS.
StartToFinish
The successor cannot finish until the predecessor has started: "the old system runs until the new one starts". Rare, but some plans need it. Written SF.
StartToStart
The successor starts once the predecessor has started, so the two can run side by side: "start the API two days into the wireframes". Written SS.