Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
while working with WF 4.0 I noticed that the WorkflowApplication class exposes action properties (Aborted, Complete, etc…) instead of events.
Is there a specific reason? When should I prefer action properties instead of events?
Thank you
I sent an email to one member of the WF team and, kindly, he answered me.
He told me that events and actions are almost equivalent, but the team had better feeling with the API using actions.