MahApps.Metro | allows developers to cobble

You will need to make use of either the Dispatcher or the DispatcherSynchronizationContext to "marshal" the call from within your Task to the main UI thread. Here's how you could use the DispatcherSynchronizationContext:

Clean Testing: You should try the package on a clean virtual to see if you have a "dirty state" on your main box - from prior experiments. It is not uncommon to find several versions of your package in Add / Remove - potentially with different names. This can happen in several ways, but usually it is because of misconfigured major upgrade settings for one or more test versions. Files are not uninstalled before all "clones" are uninstalled. There can also be other reasons for files remaining after uninstall.

List Installed Packages: You can run this script to get a list of all MSI packages installed on your machine: https://github.com/glytzhkof/all/blob/master/MsiHtmlReport-Mini-V4.vbs

Service Installation: You should not use custom actions to install services when using Windows Installer. Here is an old answer to explain why and a sample of how services are supposed to be installed:

• How to install services with WiX / MSI
• https://github.com/Robs79/How-to-create-a-Windows-Service-MSI-Installer-Using-WiX

Essentially you use the ServiceInstall and ServiceControl constructs inside the MSI.

First of all, it is better to use a to use a panel that distributes the available space among its content, like a Grid, to prevent cutting off content as with the StackPanel. Here, the data template defines a Grid with two rows, where the TextBlock scales to its desired size and the icon takes up the remaining available space. Also note the HorizontalAlignment of the icon, it is centered.

The binding errors while debugging originate from the MahApps default style for ListView. As you can see in the MahApps.Styles.ListView style, the control template contains a ScrollViewer that references a style called MahApps.Styles.ScrollViewer.GridView. This style is specific to a GridView and contains bindings to all the properties that are not found at runtime in the GridViewHeaderRowPresenter.

In other words, the default style for ListView in MahApps expects a GridView. In order to fix this, you will have to create a custom MahApps.Styles.ListView style to support your TileView.

The WrapPanel is applied in your application, but not when using MahApps. It seems that actually a VirtualizingStackPanel is applied. The MahApps default style for ListBox contains this Trigger:

You can browse the icons using their icon pack browser found here https://github.com/MahApps/MahApps.Metro.IconPacks/releases/download/4.8.0/IconPacks.Browser.Release-v4.8.0-rc0006.zip

Since file size is a concern you can use that browser to copy the path geometry so you don't have to install an entire pack just the icons you want and just reference them in your App.xaml file in a PathGeometry item to use them

I suspect this is due to virtualization. The UI items don't exist until they are scrolled into view.

Try turning off virtualization on your list control:

In order to customize the window buttons, you have to create a custom control template for the type WindowButtonCommands. You can copy one of the default control templates below from GitHub.

• MahApps.Templates.WindowButtonCommands
• MahApps.Templates.WindowButtonCommands.Win10

I took the Win10 control template and and adapted two things in the PART_Max button:

1. Change the Data of PART_MaxPath Path to an appropriate path that represents the icon or replace it with a TexBlock that uses the Segoe MDL2 Assets font and displays the gylph.
2. Change the DataTrigger for Maximized to set the appropriate icon the same way.

In the example below, I used the TextBlock approach, because I do not have path data for the icons. Please be aware, that the Path variant would always work, while the TextBlock variant requires the font to be available on your system.

To override the styles of the inner controls of the WindowCommands you must create your own style for it:

Here are the properties of the MetroWindow which changes the title bar in MahApps v2.4.x

• TitleCharacterCasing: Changes the character casing with the CharacterCasing enumeration values
• TitleForeground: Gets or sets the brush used for the titlebar's foreground
• WindowTitleBrush: Gets or sets the brush used for the Window's title bar
• NonActiveWindowTitleBrush: Gets or sets the brush used for the Window's non-active title bar