Wpf – How to deal with look-and-feel differences between standard dialogs and WPF

dialogwpf

please help resolving one look-and-feel inconsistency issue in WPF.

Look at the picture from MSDN Magazine article on Advanced WPF:

MessageBox.Show(message) is called, and why the button on it looks different than buttons on the main window?

The Open File standard WPF dialog has the same problem, only worse: on Vista it looks like old XP (if not win2k) dialog, when all other apps use new cool Vista dialogs.

So,

What explains such strange behavior of PresentationFramework?
How can I make my app use default system dialogs, with system styles, that don't look like win2k?

Best Answer

I am not an expert, but my opinion is that WPF draws all its controls in a scene graph and can apply styles to the controls. The default system dialogs are drawn with GDI and must be styled by GDI. In that screen shot, the system dialog didn't have any WPF looking style attached to it.

Related Solutions

.net – How to use WPF bindings with RelativeSource

If you want to bind to another property on the object:

{Binding Path=PathToProperty, RelativeSource={RelativeSource Self}}

If you want to get a property on an ancestor:

{Binding Path=PathToProperty,
    RelativeSource={RelativeSource AncestorType={x:Type typeOfAncestor}}}

If you want to get a property on the templated parent (so you can do 2 way bindings in a ControlTemplate)

{Binding Path=PathToProperty, RelativeSource={RelativeSource TemplatedParent}}

or, shorter (this only works for OneWay bindings):

{TemplateBinding Path=PathToProperty}

.net – What’s the difference between StaticResource and DynamicResource in WPF

A StaticResource will be resolved and assigned to the property during the loading of the XAML which occurs before the application is actually run. It will only be assigned once and any changes to resource dictionary ignored.

A DynamicResource assigns an Expression object to the property during loading but does not actually lookup the resource until runtime when the Expression object is asked for the value. This defers looking up the resource until it is needed at runtime. A good example would be a forward reference to a resource defined later on in the XAML. Another example is a resource that will not even exist until runtime. It will update the target if the source resource dictionary is changed.

Best Answer

Related Solutions

.net – How to use WPF bindings with RelativeSource

.net – What’s the difference between StaticResource and DynamicResource in WPF

Related Topic