So I’m trying to figure out how to use WF 4 as a controller for a Prism app, and already I’m running into some interesting behavior. First off, in anything but a very simple solution, custom activities don’t show up in the toolbox like they should. That’s not a huge deal, but annoying.
Of greater interest (concern?) is the fact that if I put my workflow XAML file in the main WPF app solution, everything builds and runs just fine, except the workflow does absolutely nothing. It just finished successfully, having run none of it’s activities. If I take exactly the same XAML file and put it in another assembly, then run it from the WPF app, it works just like it should. I’m guessing this is a byproduct of the new unified XAML engine, but I haven’t had time (or inclination really) to delve. Mostly it just means I have to have at least one superfluous assembly, which for now isn’t too high a price to pay.
The day I installed beta 2, I managed to crash the workflow designer about 10 times, but it seems to have settled down now. Overall, I really appreciate the new model for WF, which seems much more composable and easy to use.