1. The terminateActivity just aborts the workflow and I 'll have to do some cleaning just before getting to the terminateactivity all the time(because it does not go into faulthandler or cancellation handler). But the cleanup procedure is always the same. Furthermore I have to do this very often in serveral branches in the workflow erverytime I want to abort the workflow, so this is no solution.
   
   
2. If I raise an exception somewhere in the workflow I 'll get to the FaultHandler. The activities in there are then being executed and then the workflow continues. But it has to be aborted! So I could throw some exception again inside the faulthandler...ugly!
   
   
3. But I need something(activity) which goes into the faulthandler, cancellationhandler(or something else whatsoever) does some cleanup and then terminates the workflow(or the workflow terminates itself then).

Create a composite activity that either

a) defines your cleanup code statically, or with some properties settable by the consumer, and then ends with a terminate shape built right in.

b) allows the user to add any thing they want to it (basic derivation from a sequence) and then add the terminate in behind the scenes using a toolboxitem perhaps.

Matt