c# - Should I expose Actions instead of events? -
while working wf 4.0 noticed workflowapplication class exposes action properties (aborted, complete, etc...) instead of events. there specific reason? when should prefer action properties instead of events?
thank you
wow; see what mean; surprises me.
however, if can't think of reason use properties here (and can't), stick event
s; avoid range of problems (accidental unsubscription , inappropriate invocation being biggest).
the thing can think of maybe needed serialization purposes, can think of other ways crack nut. alternatively, maybe regular events don't make sense in crazy "dependency property" / "attached property" / "routed event" world of wf.
Comments
Post a Comment