To add on to what Ray says: For the Styles, you either need to supply a Key/ID or specify a TargetType. If a FrameworkElement does not have an explicitly specified Style, it will always look for a Style resource, using its own type as the key – Programming WPF (Sells, Griffith) If you supply a … Read more
<UserControl.Resources> <Style x:Key=”myLBStyle” TargetType=”{x:Type ListBoxItem}”> <Style.Resources> <SolidColorBrush x:Key=”{x:Static SystemColors.HighlightBrushKey}” Color=”Transparent”/> </Style.Resources> </Style> </UserControl.Resources> and <ListBox ItemsSource=”{Binding Path=FirstNames}” ItemContainerStyle=”{StaticResource myLBStyle}”> You just override the style of the listboxitem (see the: TargetType is ListBoxItem)
Referencing an external ResourceDictionary (XAML File): <Application.Resources> <ResourceDictionary Source=”MyResources.xaml” /> </Application.Resources> Referencing an external ResourceDictionary (DLL): <Application.Resources> <ResourceDictionary Source=”/MyExternalAssembly;component/MyResources.xaml” /> </Application.Resources>
Just to complete the original answer, I think it is clearer adding the nested style inside the parent like that: <Style x:Key=”WindowHeader” TargetType=”DockPanel” > <Setter Property=”Background” Value=”AntiqueWhite”></Setter> <Style.Resources> <Style TargetType=”Image”> <Setter Property=”Margin” Value=”6″></Setter> <Setter Property=”Width” Value=”36″></Setter> <Setter Property=”Height” Value=”36″></Setter> </Style> <Style TargetType=”TextBlock”> <Setter Property=”TextWrapping” Value=”Wrap”></Setter> </Style> </Style.Resources> </Style>
<TextBlock IsHitTestVisible=”False” …/>
You should use FrameworkElement.SetResourceReference if you want true DynamicResource behaviour – ie updating of the target element when the resource changes. tb.SetResourceReference(Control.StyleProperty, “FormLabelStyle”)
The setters in WPF styles are checked during compile time; CSS styles are applied dynamically. You have to specify a type so that WPF can resolve the properties in the setters to the dependency properties of that type. You can set the target type to base classes that contain the properties you want and then … Read more
Update: As a result of this discussion, the “CSS Diff” Chrome extension was created. Great question and cool idea for extension! Proof of concept As a proof of concept, we can do a small trick here and avoid creating extension. Chrome keeps elements you select via ‘inspect element’ button in variables. Last selected element in … Read more
I know this post is super old, but I have an answer that’s surprisingly missing from the above and is also much simpler than most. <Button> <Button.Resources> <Style TargetType=”Border”> <Setter Property=”CornerRadius” Value=”5″/> </Style> </Button.Resources> </Button> Since the default ControlTemplate for the Button control uses a Border element, adding a style for Border to the Button’s … Read more
You can leverage DomSanitized to avoid it. The easiest way is to create custom pipe like: import { DomSanitizer } from ‘@angular/platform-browser’ import { PipeTransform, Pipe } from “@angular/core”; @Pipe({ name: ‘safeHtml’}) export class SafeHtmlPipe implements PipeTransform { constructor(private sanitized: DomSanitizer) {} transform(value) { return this.sanitized.bypassSecurityTrustHtml(value); } } So you can use it like: <div … Read more