Skip to main content

WPF ResourceDictionaries

One thing that I noticed when using WPF ResourceDictionaries (and something that I couldn’t find anywhere in any kind of documentation) is that the order in which you add items to your ResourceDictionary is important.

So if you have a DataTemplate that refers to another DataTemplate, you’ll have to put the DataTemplate you refer to first(!).

This XAML gives an error at runtime(Notice how the LinkTemplate refers to the LinkActionTemplate):

   1:  <DataTemplate x:Key="LinkTemplate">
   2:          <StackPanel VerticalAlignment="Stretch" HorizontalAlignment="Stretch" MinWidth="106" MinHeight="35" 
   3:              Cursor="Hand" Background="Transparent">
   4:              <TextBlock Text="{Binding Title}" TextWrapping="Wrap"/>
   5:              <ItemsControl ItemsSource="{Binding ChildNodes}"
   6:                  ItemTemplate="{StaticResource LinkActionTemplate}"/>
   7:          </StackPanel>
   8:  </DataTemplate>
   9:      
  10:     
  11:   <DataTemplate x:Key="LinkActionTemplate">
  12:          <StackPanel Orientation="Horizontal" Margin="20,2,0,2" MinHeight="22" Cursor="Hand">
  13:              <Image Source="{Binding IconPath}"  />
  14:              <TextBlock Text="{Binding Title}" >
  15:              </TextBlock>
  16:          </StackPanel>
  17:   </DataTemplate>
  18:      
  19:


This XAML works fine:


   1:      <DataTemplate x:Key="LinkActionTemplate">
   2:          <StackPanel Orientation="Horizontal" Margin="20,2,0,2" MinHeight="22" Cursor="Hand">
   3:              <Image Source="{Binding IconPath}"  />
   4:              <TextBlock Text="{Binding Title}" >
   5:              </TextBlock>
   6:          </StackPanel>
   7:      </DataTemplate>
   8:   
   9:   
  10:      <DataTemplate x:Key="LinkTemplate">
  11:          <StackPanel VerticalAlignment="Stretch" HorizontalAlignment="Stretch" MinWidth="106" MinHeight="35" 
  12:              Cursor="Hand" Background="Transparent">
  13:              <TextBlock Text="{Binding Title}" TextWrapping="Wrap"/>
  14:              <ItemsControl ItemsSource="{Binding ChildNodes}"
  15:                  ItemTemplate="{StaticResource LinkActionTemplate}"/>
  16:          </StackPanel>
  17:      </DataTemplate>
  18:
Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...
Read more