Well guys, here is my freshly baked article @ CodeProject.
I am quite excited about this writing, coz it’s a huge task that I will be working on in the next couple of months. Anyways best of luck to ME! :}
With the advent of .NET Framework 3.0 (formerly WinFX), terms like Windows Presentation Foundation (formerly Avalon), Communication Foundation (formerly Indigo), Workflow Foundation (formerly WWF) and Cardspace (formerly InfoCard) are everywhere. The .NET Framework 3.0 also includes a powerful general-purpose object initialization language known as XAML (eXtensible Application Markup Language). What Microsoft is really putting stress on is creating compelling user experiences and secure, seamless communication across boundaries.
In this series of articles, I will be explaining and going in depth with some of the core components of .NET Framework 3.0.
Let’s start with Windows Workflow Foundation (WF).
I assume you have basic knowledge of the .NET Framework. I will try and cover most of the concepts as soon as they arise.
Workflow and its types
In the business world, workflow is simply a business process (independent of technology) necessary to complete a task. There can be various steps involved in any business process that can be either optional or required. So simply put, “workflow” is just the flow of work.
If we add more to it, “flow of work” can be either in a sequential manner (i.e. steps are performed one after another), or there could be several points in the flow where some decisions need to be made. Since a flow cannot move from one point to another without some criteria being met, we have a state-based workflow.
Thus, we can simply say there are two types of workflow:
………………rest on code project 🙂