When I first started looking into Windows Workflow one of the first things that I liked about it was how it separated responsibilities. The workflow was responsible for handling the procedural logic with all its conditional statements, etc. Whilst individual code activities could be written to handle the business logic processing; created in small easily re-usable components. To try and realise my original perception this series of blog posts will cover the unit testing of . . .
As part of my day job I’ve been experimenting with Windows Workflow in both modifying the existing TFS2010 build templates and as a way of controlling the process flow in our new suite of applications. On the most part I’ve been really impressed; when you sit in a process workshop watching the business users mapping the existing steps out on a whiteboard (or even a wall) it is quickly apparent that showing them a similar . . .
Just as I start getting up to speed with WF4.0 MSDN magazine publishes an article detailing what’s new in WF4.5. It looks like there’s a lot of good stuff coming but the main thing that I noticed was that v4.0 requires full-trust to run. That shouldn’t be a problem for the project we’re intending to run the workflow in, but if it will run in partial trust in the next release that will open up . . .
I’ve been trying to find workflow resources on Twitter but unlike some other technologies, there doesn’t seem to be much regular traffic. The hashtag #WF4 does seem to be used and I’ve started a twitter list of people I find regularly talking about WF4.0 on-line.
Today I’ve started learning about Windows Workflow v4.0, I’m hoping that it will help out with a current project. The original requirement was for mapping real-world business processes to what would normally be complex long-running computer tasks. Whilst investigating what it could do I’m beginning to think there could be real value using it for any task that requires process flow logic, even extremely short-lived ones. This could be controlling page flow through a web . . .