Merge dictionaries does not work when we merge merged dictionaries - by DrWeb86

Status : 


Sign in
to vote
ID 609601 Comments
Status Closed Workarounds
Type Suggestion Repros 0
Opened 10/2/2010 8:33:49 AM
Access Restriction Public


Suppose we have merge dictionary GridRes where we override several templates for grid

Suppose we have resource dictionary AllResources where we merged GridRes

Suppose we have a form with a grid where we programmatically or via xaml loaded AllResources as merged dictionary.

Override templates were not overrided with redefined for grid (but when we copy them from gridRes to Resources of window all goes fine)

So mergeddictionary's merged dictionaries are not handled well.
Sign in to post a comment.
Posted by dwaldo on 8/15/2014 at 11:25 PM
Interesting that this only has roughly 10 votes. The web is full of questions relating to this.

etc. Google/Bing it if you really want to know how bad the issue is :)
I'm frustrated, trying to make a Prism app, and think oh yah, I'll start putting all my styles into dictionaries, oh yah have to merge them... BOOOM, oh yah, that's why my styles are in dictionaries, cause life kinda sucks when you try to do things right with wpf :)
Posted by Microsoft on 11/15/2012 at 3:29 PM
The WPF team has recently reviewed this issue and will not be addressing this issue as at this time the team is focusing on the bugs impacting the highest number of WPF developers. If you believe that this was resolved in error, please reactivate this bug with any necessary supporting details.

We appreciate the feedback. However, this issue will not be addressed in the next version of WPF. Thank you.
–WPF Team.
Posted by arnie on 5/11/2011 at 3:15 PM
We see the same thing.

When we nest merge dictionaries together of 3 levels or deeper things don't work. The suggested workaround to create a "dummy" default style at the root or anywhere else also doesn't fix anything. Seems like a bug to me.Please fix.
Posted by Microsoft on 10/3/2010 at 6:21 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(