It can't see it because it's essentially replacing it. The InitializeComponent method call will replace the dictionary you refer to in your ctor with the dictionary you define in your XAML Basically, you're doing it wrong. Why can't you just do this: UserControl.Resources.
It can't see it because it's essentially replacing it. The InitializeComponent method call will replace the dictionary you refer to in your ctor with the dictionary you define in your XAML. Basically, you're doing it wrong.
Why can't you just do this.
This is what I thought was happening, but it isn't. The dictionaries merged in code are available to the rest of the control and dynamically to resources of UserControl, regardless of whether a Resources is defined in XAML. – Adam Mills Jul 7 at 13:04 we have a composite app, each module is independently styled.
A custom UserControl base class which injects common styles is the only way we can think of to get an App. Xaml equivalent of global module styles. Don't want to have to link them into every control – Adam Mills Jul 7 at 13:06.
It can't see it because it's essentially replacing it. The InitializeComponent method call will replace the dictionary you refer to in your ctor with the dictionary you define in your XAML. Basically, you're doing it wrong.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.