> First, to clarify on the statement about the `QualifiedModuleName`: it is not about mapping a declaration to a component. It is a proxy for a component that reduces COM access by caching the most important properties, in particular those needed to identify a component.

In my humble opinion, we should not ban the `QualifiedModuleName` from the `QualifiedMemberName` on the declaration, but refactor split it in two parts. In 90% of all uses, we only need the cached information. So, my proposa

> With AvalonEdit coming, the Ribbon XML files can be displayed as source-code pages (instead of as dedicated ToolWindows). I've added CustomUI and CustomUI14 properties to IVBProject in my branch, so the ribbon content is nearly available. We'll just need to be able to have AvalonEdit be able to render XML source, and select nodes where there's a callback method defined.

I've also added a list of callbacks by control and callback signature, so hopefully find usages will be able to resolve th

> In relation with the discussion in #3534, I am not sure how moving the default hotkeys into a `.settings` file will help with dependency injection circularity. When loading the default hotkeys, some component (most likely the `DefaultSettings` class) will need to have `IEnumerable<CommandBase>` injected to know what commands are available for hotkey binding at runtime.

I see another issue: serializing/deserializing the commands that were assigned to hotkeys. If I assign a `CommandBase` inst