I downloaded the samples and went through the basic shapes section. All fine here.
But my impression is about to change, as Workflow 4 seems to contain a number of serious bugs.
This becomes very evident if you look at the execution of the finally block in a try/catch activity.
According to msdn...
"The finally block is useful for cleaning up any resources allocated in the try block as well as running any code that must execute even if there is an exception. Control is always passed to the finally block regardless of how the try block exits."
The most simple form of a try-Catch Activity is this:
Please note that there is no Exception handler in the "Catches" section. I simply want the Exception to propagate, but before it does that I want to make sure my code block in finally is executed no matter what happens.
But if you now execute the code, you will find out that the code in our finally block never gets executed....
This will not change if you add an exception handler, that does not handle the specific exception.
To make things worse we will see, that even if we handle the specific exception and and want to rethrow it, our finally is never executed.
Actually the only time the finally gets executed in case of an exception is when the Exception is handled and not propagated.
In Workflow 4 you cannot propagate an exception and execute a finally block.
In other words:
You cannot use a finally block.
Update: In the MSDN Forum Steve Danielson gave an excellent hint on the difference between C# Try/Catch and Workflow Try/Catch.