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

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...

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.

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...