Understanding Windows Workflow Foundation: Key Concepts and Features
Learn about Windows Workflow Foundation (WF), one of the core pillars of .NET 3.0, its workflow types, hosting options, scheduler services, persistence services, challenges like versioning, and insights from a Readify developer network session.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.
E N D
Presentation Transcript
Windows Workflow Foundation David Burela Senior Developer, Readify Discover, Master, Influence 1
What is WF? Stands for Windows Workflow Foundation (not WWF .) One of the 4 pillars of .NET 3.0 Way to declaratively create workflows that can be hosted in applications
Workflow types Sequential Starts at the top. Flows downwards Production line State machine Goes from one state to another Document management system
Hosting WF Workflows can be hosted in any .Net app Console, winforms, WPF, ASP.Net Integration into other Microsoft tech Sharepoint Biztalk WCF
Demo HAMBURGER CONSTRUCTION
Scheduler service DefaultWorkflowSchedulerService Asynchronous scheduling of workflow instances (Client hosting) ManualWorkflowScheduler Service Synchronous scheduling (Server hosting) Choosing scheduler service is important
Persistence Service Persistent Services are used to persist state about a Workflow instance The Workflow runtime engine determines when persistence should occur Protects against power loss, etc. Reduces memory footprint
Versioning Massive pain point Persistence problems Changing code in an activity may be fine Restructuring will come up against problems Research on the web!
A Readify Developer Network session By David Burela, Senior Developer, Readify Email Address: Resources on Blog: http://DavidBurela.wordpress.com David.Burela@readify.net Discover, Master, Influence 9
