Rick Garibay has two very interesting posts on the changes that WF 4.0 will bring and the impact on existing WF 3.5 apps:
Copy of some important points:
- WF developers should stop using custom code activities and opt for custom activities instead.
- In WF 4.0, all aspects of an activity are represented as XAML. Most importantly, this includes variables within each activity which are bound as input/output parameters from one activity to another. This is a significant change from 3.5 because variables are no longer scoped at the global workflow level, but instead are scoped to the activity level.
- Should we continue to build composable service-oriented applications with WF 3.5 or bite the bullet and build on early WF 4.0 bits? Well, according to Cliff Simpkins, Office 14 is shipping with 3.5, and if Microsoft is willing to invest this heavily in 3.5 in a brand new product that hasn’t shipped, you can imagine that it should be suitable for LOB applications as well as the enterprise.
