Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>OK, finally, I found out what was the problem. In the first post I wrote that at first everything worked just as charmed but after some little changes,that should not influence the persisting of the workflow, Sql Workflow Persistence Service was not able to save the state in database.</p> <p>What I didn't mention the I exposed workflow as a WCF Service, and it turns out that crucial to solve this problem. I apologize to everybody that tried to solve this whit lack of information.</p> <p>I used the Receive Activity which I pointed to the method WCF Service contract. That method had a return value of complex type: </p> <pre><code>[DataContract] public class ServiceCallInfo { int code; [DataMember] public int Code { get { return code; } set { code = value; } } string message; [DataMember] public string Message { get { return message; } set { message = value; } } } </code></pre> <p>I binded that return value to the new property of the workflow.</p> <pre><code>public static DependencyProperty ReturnInfoProperty = DependencyProperty.Register("ReturnInfo", typeof(my.mynamespace.ServiceCallInfo), typeof(my.mynamespace.StandardContractingWorkflow)); [DesignerSerializationVisibilityAttribute(DesignerSerializationVisibility.Visible)] [BrowsableAttribute(true)] [CategoryAttribute("Parameters")] public my.mynamespace.ServiceCallInfo ReturnInfo { get { return ((my.mynamespace.ServiceCallInfo)(base.GetValue(my.mynamespace.ReturnInfoProperty))); } set { base.SetValue(my.mynamespace.ReturnInfoProperty, value); } } </code></pre> <p>If I only instantiate this property somewhere in the code of the workflow, Workflow Runtime fails to save the state, and if I don't do that state is saved properly! I assume that, for some reason, Workflow Runtime was not able to serialize (or whatever it does to save the state using Sql Workflow Persistence Service) workflow state because of this property.</p> <p>Maybe it's because of definition of ServiceCallInfo class, maybe it's something else... I hope that someone with more knowledge and experience will be able to say what were the real reasons...</p> <p>However, this problem is solved.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload