Agreed - I wanted to make a client endpoint behavior but it turns out that you cannot intercept a call on the client. There are other ways to do this but they involve messing with the client proxy typically.
@srikalyan: well for people who need to generate services from XSD this is a nice convenience. Otherwise they have to do quite a bit of work with svcutil. Of course if you don't have the need to build services from XSD then it doesn't help you much.
Thanks for the feedback - I hear you. We want to provide ways to work with exisitng mocking frameworks when possible. XAML based workflows are in a special category of thing that other mocking frameworks can't really help you with. Of course once you cross over into the code of an activity then you can always mock at that level with whatever you like
I have not done any direct performance comparisons to a Windows Service doing the same work. It seems to me that for most things the performance should be close to the same since mostly they are waiting for work to do. Having the workflow with AppFabric
doing the job gives you the added benefit of the monitoring store which is really cool for this sort of thing.