You don't have an App.xaml to define the application's resource dicts. Suspect I've got choices of either...
Having a xaml resource dictionary which I can reference as a header for each view.
Having the viewmodels define what their resources are. This sort of breaks the separation of responsibilities, but if it works, and since it's only the installer, whatever.
var dictionaries = App.Current.Resources.MergedDictionaries;
dictionaries.Clear();
var themeStyles = new ResourceDictionary { Source = new Uri("/MyAssemblyName;component/Styles/Styles.xaml", UriKind.RelativeOrAbsolute) };
dictionaries.Add(themeStyles);
You're going to need up your xaml game for this.
You don't have an App.xaml to define the application's resource dicts. Suspect I've got choices of either...
Having the viewmodels define what their resources are. This sort of breaks the separation of responsibilities, but if it works, and since it's only the installer, whatever.
See also refs: https://msdn.microsoft.com/en-gb/library/cc903952%28v=vs.95%29.aspx?f=255&MSPPError=-2147217396 http://stackoverflow.com/questions/11116033/referencing-resource-dictionaries-in-a-separate-project