So, here are two classic questions.
1. When should we use WF - workflow?
When we are going to design a long run application.
for example, document approval system. Leave Request application, Over Time work Submit system. etc.
All this applications have one common characteristic: long run
2. Why do we need WF?
Simply put, If we write everything in code from scratch, we have to do a lot of tedious things such as persistence, tracking, tracing, bookmark... . these boring things make developer's life hard. and now Microsoft do all sweaty jobs for us.
We learn it, use it and make life better, that is why we use Windows Workflow Foudnation - WF
You can start from here:
Introduction to Workflow 4.0
http://channel9.msdn.com/learn/courses/VS2010/WCFWF/IntroToWF/
To learn more about WF4, read the WF4 document:
http://msdn.microsoft.com/en-us/library/dd489441(v=VS.100).aspx
To learn how to apply WF4 in real applications, check samples:
http://msdn.microsoft.com/en-us/library/dd483375(v=VS.100).aspx
To get deep into WF4, follow this blog(go with flow):
http://blogs.msdn.com/flow/default.aspx
and this one (matt's blog)
http://blogs.msdn.com/mwinkle/default.aspx
And .NET endpoint:
http://blogs.msdn.com/endpoint/default.aspx:
If you can read Chinese, I recommend you read through this blog:
http://www.cnblogs.com/foundation/
If you get any problems, Ask your question in WF4 forum:
http://social.msdn.microsoft.com/Forums/en-US/wfprerelease/threads
2329a8f7-46cb-4666-896a-963d207f2f79|1|5.0
WF4