Since that’s the third time I’ve been asked about it, and in fact came across the problem myself, I thought I should blog my reply to help future users.
You use the Windows Ribbon Framework, either directly (in C++) or in managed code using my Windows Ribbon for WinForms library. You add a close button to the ribbon which closes the application. The application crash on close.
Don’t cut the branch you sit on
The problem is that you try to call ribbon.DestroyFramework, which ultimately calls IUIFramework.Destroy from a ribbon command handler. So while handling the ribbon event you try to kill the ribbon. It is only fair that the ribbon control fights back..
Either invoke the Close() method asynchronously:
// Close form asynchronously since we are in a ribbon event
// handler, so the ribbon is still in use, and calling Close
// will eventually call _ribbon.DestroyFramework(), which is
// a big no-no, if you still use the ribbon.
or don’t call DestroyFramework when closing the application (and trust windows for releasing the resources).
[By the way, the C++ solution is simply to call PostMessage(WM_CLOSE) instead of SendMessage(WM_CLOSE)]
I’ve updated sample 04-TabGroupHelp on the project site so that it has a real exit button on the ribbon that closes the form.
That’s it for now,