Splitting the Ribbon controls in separate files breaks the QAT functionality.

It seems this is because I have in place bindings to DataContext like DataContext="{Binding TestTab}" or DataContext="{Binding TestGroup}" and somehow the QAT RibbonControlPath searches using the MainViewModel.

It seems that I need the full path inside the button bindings and not like I am doing here.

Hi Daniel,

The QAT serialization logic will try to locate a set of path items to point to another control already in the Ribbon with the same Id if it can.  If one is found, it will try to use the CloneService to clone that existing control within the ribbon on QAT layout deserialization.  It's a good idea to assign Id property values in all controls that can be placed in the QAT if you will be doing QAT serialization.

If it is unable to serialize a full path to a control, it will try to serialize an element instance instead.  For that it will use XamlSerializer to write out the XAML of the control to a string, and will use XamlSerializer to load later on as well.  Things like Bindings will not serialize properly with XamlSerializer and it will serialize the binding's resolved value instead.

This all is another area where our newer Bars ribbon control implementation is much improved, especially when using MVVM.  With that, it creates a simple minimal string for QAT serialization that doesn't run into any of these issues.