Is there a significant performance cost to DynamicResource instead of StaticResource?
Our designer is using Blend to style our WPF application. When he chooses local resources for properties, Blend will apply them as a {DynamicResource} instead of a {StaticResource} . My guess is that Blend does this because it enables the app to be re-themed at runtime without having to restart it. My question is: is there a significant performance cost to this additional lookup? Should we ask the designer to go back and manually change those Dynamics to Statics? Here is a great SO question that explains the difference between the types: What's the difference between StaticResource and