Skip to main content

Caliburn.Micro: Design time support

WPF and Caliburn.Micro are a powerful combination. You create a viewmodel and related view, name your controls appropriately  and all magic happens automatically. Controls are bound to the View Model’s properties and methods for you. The problem is that it is all happing at run time not at design time. So when you are developing inside Visual Studio or Expression Blend you aren’t able to see how the form will look like with bound data.
Caliburn.Micro supports design-time binding out-of-the-box. How can we configure this?
In the constructor of my ViewModel, I check if we are executing in design time:
public class SampleViewModel : Screen
{
 public SampleViewModel()
 {
  if (Execute.InDesignMode)
         LoadDesignData();
 }
}
In this sample I populate my ViewModel with some sample data at design time.

private void LoadDesignData()
{
 this.Sessions.Add(new ProfilerSessionViewModel() { Id = Guid.NewGuid(), Duration = "30ms", Name = "Session 1", Started = DateTime.Now.AddMilliseconds(-30) });
 this.Sessions.Add(new ProfilerSessionViewModel() { Id = Guid.NewGuid(), Duration = "30ms", Name = "Session 1", Started = DateTime.Now.AddMilliseconds(-30) });
 this.Timings.Add(new TimingViewModel() { Duration = "30ms" });
 /*Removed some lines*/
    this.Queries.Add(new QueryViewModel() { CallStack = "", Duration = "10", NrOfRecordsAffected = 92, Query = "SELECT * FROM Products", QueryType = "ExecuteDataReader", Step = "Executing query", TimeFromStart = "3" });
}

In my view I added the following code:

<Window x:Class="VLM.SOFA.Profiling.Win.UI.ProfilerView"
xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006" 
xmlns:d="http://schemas.microsoft.com/expression/blend/2008"
mc:Ignorable="d" 
xmlns:cal="clr-namespace:Caliburn.Micro;assembly=Caliburn.Micro"
xmlns:vm="clr-namespace:VLM.SOFA.Profiling.Win.UI"
d:DataContext="{d:DesignInstance Type=vm:SampleViewModel, IsDesignTimeCreatable=True}"
cal:Bind.AtDesignTime="True">
</Window>


I set the Bind.AtDesignTime property of Caliburn.Micro to true, create an ignorable alias “d” and assign an instance of my viewmodel to my design time datacontext.

And now we have nice design time support:

image

Popular posts from this blog

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.

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         ...

Cleaner switch expressions with pattern matching in C#

Ever find yourself mapping multiple string values to the same result? Being a C# developer for a long time, I sometimes forget that the C# has evolved so I still dare to chain case labels or reach for a dictionary. Of course with pattern matching this is no longer necessary. With pattern matching, you can express things inline, declaratively, and with zero repetition. A small example I was working on a small script that should invoke different actions depending on the environment. As our developers were using different variations for the same environment e.g.  "tst" alongside "test" , "prd" alongside "prod" .  We asked to streamline this a long time ago, but as these things happen, we still see variations in the wild. This brought me to the following code that is a perfect example for pattern matching: The or keyword here is a logical pattern combinator , not a boolean operator. It matches if either of the specified pattern...