Previously, I had success using RecentDocumentManager via XAML when the RecentDocumentManager object was inline in the XAML. However, I'm now trying a more MVVM approach, and data binding to a RecentDocumentManager property on my ViewModel.
It works great if my BackstageTab is also inline XAML. However, if I instead use a Style for my BackstageTab, it fails.
I've created a very small simple project which demonstrates the issue. I'd be happy to send it to you.
The problem is that the Documents never show up in the Styled and Data-bound case. I've used Snoop on it, and it appears the RecentDocumentMenu.Manager property has a Local value. If I do the Snoop Clear/Reset on Manager, it suddenly works, and becomes a ParentTemplate value.
I'm wondering if this is an example of the DependencyObject.SetCurrentValue() issue.
[Modified at 02/16/2012 12:25 PM]
It works great if my BackstageTab is also inline XAML. However, if I instead use a Style for my BackstageTab, it fails.
I've created a very small simple project which demonstrates the issue. I'd be happy to send it to you.
The problem is that the Documents never show up in the Styled and Data-bound case. I've used Snoop on it, and it appears the RecentDocumentMenu.Manager property has a Local value. If I do the Snoop Clear/Reset on Manager, it suddenly works, and becomes a ParentTemplate value.
I'm wondering if this is an example of the DependencyObject.SetCurrentValue() issue.
[Modified at 02/16/2012 12:25 PM]
