I understand. This is how it works, currently. (The subscriptions are inherently different; same with EasyXXClient.SubscribeXXXX - it does not block when there is a problem, too).

A possible workaround with the current version (not entirely code-less, though):

1. Do not configure the WriteEventSource (button1.Click, in your case) on the binding.

2. Instead, double click on the button in the designer, and let VS create an event handler for the click event.

3. Figure out the member name of the binding. Can be done by clicking on the bindingExtender1 below the form surface; then, in the Properties window, expand ("+") the ComposedBindingBag, select the Bindings row underneath it, and click "..." next to it. You will see a collection editor form. The member names are in the right part under Design -> (Name), and will look like "daItemBinding1" etc.

4. Fill in the event handler from Step 2 with following code, replacing the binding member name as appropriate:
This should do it.


I take this as a very useful suggestion for improvement. It would be best if the developer is given a choice of which behavior she wants. More on this in an email to you that will follow.

Best regards