resourcedictionary

Given that I have a shell application and a couple of separate module projects using Microsoft CompoisteWPF (Prism v2)... On receiving a command, a module creates a new ViewModel and adds it to a region through the region manager. var viewModel = _container.Resolve<IMyViewModel>(); _regionManager.Regions[RegionNames.ShellMainRegion].Add(viewModel); I thought that I could then create a resource dictionary within the module and set up a data template to display a view for the view model type that was loaded (see below xaml). But when the view model is added to the view, all I get is the view

I have a few WPF applications and I want all my styles to be in a shared assembly instead of declaring them in each application separately. I am looking for a way so I don't have to change all my Style="{StaticResource BlahBlah}" in the existing applications; I just want to add the reference to this style assembly, and delete it from the current application, so it's taken from the assembly. Is there any way? Shimmy Referencing an external ResourceDictionary (XAML File): <Application.Resources> <ResourceDictionary Source="MyResources.xaml" /> </Application.Resources> Referencing an external

i have a problem with Resource dictionaries and mergeddictionaries in general, especially when it comes to resource-lookup performance. After some performance testing i found that ResourceDictionary.get_MergedDictionaries is the call with the most hits (checked in ANTS profiler). We have around ~300 resource dictionary xamls, and a lot of them are using merged dictionary to "include" other styles. Well the get_MergedDictionaries count on one part of our application, where not much is happening, was around 10 million hits. So my guess is we are doing something completely wrong with Resource

Can I define a Binding as a Resource and then reuse it with different Controls properties? Example: Binding: <Window.Resources> <Binding x:Key="MyBinding" Path="MyProperty" Mode="TwoWay" /> </Window.Resources> Reuse in XAML: <TextBox Text="{StaticResource MyBinding}" /> After declaring Binding as above I got the error: "The name 'InitializeComponent' does not exist in the current context" Is there any way to reuse the same Binding in different contexts? Direct answer to your question is "yes, you can define a binding as a resource". The problem here is how do you then make any use of it? One