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?
Windows Workflow Foundation provides the Tracking services to track the status of workflow instances. Specify Code Conditions: programmatically define whether certain paths of the workflow are run. This is similar to specifying a condition in an If Statement, in traditional programming.
WF4 provides a clean and simple declarative programming framework to model business processes and services.
After you've installed the Windows Workflow Foundation component, select File > New > Project. Search for and select a workflow project template, for example, the Workflow Console Application template. Continue through to create the project.
You may need WF only if any of the following are true:
For more details, see Paul Andrew's post: What to use Windows Workflow Foundation for?
Please do not confuse or relate WF with visual programming of any kind. It is wrong and can lead to very bad architecture/design decisions.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With