MaterialDesignInXamlToolkit | Google 's Material Design in XAML & WPF , for C # & VB.Net

Turns out, this from the tutorial works.

Either install the NuGet package and reference the resource dictionaries in the App.xaml file of the consuming application, or install the package and reference the same resource dictionaries in the control itself in the library:

I do not understand, why.

Most probably because the implementation of myApp.LongRunningProcess() is not asynchronous and blocks the UI thread.

This has nothing to do with MaterialDesignInXamlToolkit "and some rendering specifics".

You need to make sure that myApp.LongRunningProcess() doesn't block.

If you replace await myApp.LongRunningProcess().ConfigureAwait(false); with await Task.Delay(2000) and you then see the "Process started..." message, you know that the implementation of myApp.LongRunningProcess() is indeed the issue.

A method is not automatically asynchronous just because it returns a Task or a Task.

In general, you can get any MaterialDesignColor using the SwatchHelper.

You could use the VisualTreeHelper class to get a reference to the Path in the ToggleButton in the default template and then set its properties:

Let's try something simple fo you to try at the first time.

The DialogHost is composed of two major parts

• First everything that is displayed into your DialogHost, this have to be into one block (StackPanel, Grid, DockPanel...) that is the content of your DialogHost.
• Second part is more like the context of your dialog, when you want to display it have to be somewhere to be displayed, another block (StackPanel, Grid, DockPanel...), the context is the place where your dialog will be once displayed, il will show centered and darken the rest of the block.

Now you have the main theory let's make a simple sample based on the sample given by the demo and your piece of code.

All seems to look right for me.

In your ShowDialog() method you only pass a string "test" as content for your DialogHost and you didn't define a DataTemplate in DialogHost.DialogContentTemplate nor a DataTemplateSelector in DialogHost.DialogContentTemplateSelector. So the default behavior of ContentControl kicks in when there is no ContentTemplate or ContentTemplateSelector defined and you don't pass the XAML elements directly as Content. This results in a TextBlock element being created for the dialog content where your string is bound to its Text property. This is exactly what your picture shows.

So to get a different result than what your picture shows you need to either pass directly your XAML elements which you want to show in your dialog (with a root container element and all buttons your dialog needs) or define a DataTemplate or DataTemplateSelector for your DialogHost in your XAML, if you want to use it in a MVVM scenario.

Look at this example from the repo if you need a hint how you can implement this.

The DialogHost does not need to be registered. When you place a dialog host instance in XAML like below, the dialog instance will be registered automatically.

You need to place your button inside of your DialogHost, if you do not specify a CommandTarget.