Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
The help topic page on ComponentResourceKey doesn’t give great guidance on when you would want to move from a string-based key to a ComponentResourceKey for putting and/or retrieving resources from a ResourceDictionary. Does anybody have any insight on when you would want to use a ComponentResourceKey over a string?
From what I understand about ComponentResourceKeys is that they establish global uniqueness by defining themselves with respect to a type, and are required for referencing resources defined in generic or theme dictionaries.
Resources you store in a theme dictionary (eg generic.xaml) are only accessible via ComponentResourceKey and not a normal x:Key UNLESS you explicitly reference the generic.xaml into the MergedDictionaries collection of a Resources collection (eg at the App or Window or element level) but you should not do this as this is not the intent of generic.xaml