Miguel is fast - here's his response:
There's a reason I didn't do that to begin with, and it goes with the reason why I broke out the extender itself from the binding components that drive it. Microsoft provided an interface, IButtonControl, for all to obey when writing custom buttons and links. So far, I've encountered that all the major component vendors use this for their buttons and links. This is the reason the extender works great with third-party controls. Microsoft provided no such interface for the creation of toolbar items. Everyone's toolbar is completely different and has no point of commonality or abstraction. So I provided the BindingHelper component so that you can have the same functionality that the extender provides for you regarding binding, unbinding, undoing, etc. It takes code, but not nearly as much as doing it all manually. I have a sample project which I forwarded you, but am attaching here, that demonstrates both cases with two identical forms. One form uses buttons, the other uses a toolbar.
Copyright (c) Marimer LLC