The past two weeks I have been touring Florida speaking on WF4.5. Last week I spoke in Tallahassee, Florida to Capital City .NET User Group and literally just finished speaking at Orlando's Code Camp. Both presentations were packed and it was good to see that WF is becoming more popular. While speaking in Tally, I was able to speak longer to the user group, but today I was rushed since the sessions are scheduled back to back.
If you attended my session today, you would have witnessed that my last demo on "dynamic update" failed. This was partially because I was rushed, but what actually caused the failure? Well just before I started on this post I was able to research my issue. My scenario revolved around the state-machine workflow below...
I had done everything I needed to do for updating the workflow so that when a customer returned a movie they rented, a list of latest movies would be presented as a way for them to rent another movie, rather then just walking away. The problem was that I never unloaded the workflow from the initial rental before making the updates to the workflow. So what I did was simply recall the persisted workflow instance that had been rented and unloaded it formally. The ReturnMovie bookmark was then set, which allowed the renter to see a list of movies where originally just a message was presented to the customer thanking them for the rental.
If you want to see more about the presentation, please check out my book titled, Pro WF4.5 and the code that is provided with the book!