The activity '{1}' cannot reference activity '{0}' because activity '{0}' is already referenced elsewhere in the workflow and that reference is not visible to activity '{1}'. In order for activity '{0}' to be visible to activity '{1}', it would have to be a child or imported child (but not an implementation child) of activity '{2}'. Activity '{0}' is originally referenced by activity '{3}' and activity '{1}' is in the implementation of activity '{2}'.
The Abort implementation of a persistence participant of type '{0}' threw an exception. Exceptions should not be thrown from ...
The action {0} is not supported by this endpoint. Only WS-ReliableMessaging February 2005 messages are processed by this ...
The ActiveStepIndex must be less than WizardSteps.Count and at least -1. For dynamically added steps, make sure they are ...
The activity '{0}' cannot be referenced by activity '{1}' because the latter is not in another activity's implementation. ...
The activity '{1}' cannot reference activity '{0}' because activity '{0}' is already referenced elsewhere in the workflow ...
The activity author supplied RuntimeArgument named 'Result' must be bound to the argument returned by the activity's Result ...
The activity author supplied RuntimeArgument named 'Result' must have ArgumentDirection Out and type {0}. Instead, it has ...
The Activity declaring ActivityDelegate '{0}' was not found in the parent hierarchy of the currently executing activity '{1}'. ...
The activity definition object for '{0}' appears to be shared between multiple nodes in the workflow. It is incorrect to ...