I've been looking at other threads for this answer and it does not seem to exist. The DynamicActivity created by ActivityXamlServices cannot be scheduled as a child of another Activity (for instance a NativeActivity) unless it is instantiated in the
constructor, which precludes using an input argument as a database key.
My conclusion is that the only pattern for storing XAML in a database is when the XAML contains the entire Workflow. This is not very useful if you want to dynamically select your Workflow based on some parameter that may be an input argument to
For my application, this greatly limits the usefulness of WF 4.0.
Does anyone have a solution to this problem?------------------------
View Complete Post