workflow-foundation

Workflow Design Dilemma - State Machine, yes or no

被刻印的时光 ゝ 提交于 2019-11-27 04:04:34
问题 I'm a beginner with WF, but I've read a book and done a lot of googling. I want to write an inventory management service. The inventory is made up of individual items which have a state: Spare Installed In-Repair Items may spend months in each state, and there are thousands of items. The question is, do I create a state machine workflow for all the different states? Or do I create workflows for transitioning between states? If I understand correctly, if I create a single state machine

What is a dependency property?

这一生的挚爱 提交于 2019-11-26 17:09:51
What is a dependency property in .Net (especially in WPF context). What is the difference from the regular property? Matt Hamilton Dependency properties are properties of classes that derive from DependencyObject, and they're special in that rather than simply using a backing field to store their value, they use some helper methods on DependencyObject. The nicest thing about them is that they have all the plumbing for data binding built in. If you bind something to them, they'll notify it when they change. The only explanation I found helpful and well written is this one: http://www

When to use Windows Workflow Foundation? [closed]

≡放荡痞女 提交于 2019-11-26 12:49:24
问题 Some things are easier to implement just by hand (code), but some are easier through WF. It looks like WF can be used to create (almost) any kind of algorithm. So (theoretically) I can do all my logic in WF, but it\'s probably a bad idea to do it for all projects. In what situations is it a good idea to use WF and when will it make things harder then they have to be? What are pros and cons/cost of WF vs. coding by hand? 回答1: You may need WF only if any of the following are true: You have a