Comments on: WPF: Inconsistent FileDialogs on Vista 64-bit. http://kristofmattei.be/2009/02/23/wpf-inconsistent-filedialogs-on-vista-64-bit/ A blog on my experiences in programming, work, and life! Wed, 08 Feb 2012 23:31:45 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Kristof's Blog :: WPF: Inconsistent FileDialogs on Vista 64-bit. #2 http://kristofmattei.be/2009/02/23/wpf-inconsistent-filedialogs-on-vista-64-bit/comment-page-1/#comment-1686 Kristof's Blog :: WPF: Inconsistent FileDialogs on Vista 64-bit. #2 Tue, 21 Apr 2009 06:17:07 +0000 http://kristofmattei.be/?p=610#comment-1686 [...] Brewster made this comment on my previous post about the Inconsistent [...] [...] Brewster made this comment on my previous post about the Inconsistent [...]

]]> By: Rick Brewster http://kristofmattei.be/2009/02/23/wpf-inconsistent-filedialogs-on-vista-64-bit/comment-page-1/#comment-1678 Rick Brewster Thu, 16 Apr 2009 00:46:12 +0000 http://kristofmattei.be/?p=610#comment-1678 Oops, that comment above should list the 3 options are 3 separate ways to achieve the same result. Not 3 things which must be done together or in sequence. Oops, that comment above should list the 3 options are 3 separate ways to achieve the same result. Not 3 things which must be done together or in sequence.

]]> By: Rick Brewster http://kristofmattei.be/2009/02/23/wpf-inconsistent-filedialogs-on-vista-64-bit/comment-page-1/#comment-1677 Rick Brewster Thu, 16 Apr 2009 00:45:37 +0000 http://kristofmattei.be/?p=610#comment-1677 This happens because you're pulling in the old version of comctl32.dll. 1) Add a manifest to your EXE that specifies version 6 of comctl32.dll. 2) Call System.Windows.Forms.Application.EnableVisualStyles. Downside is that you're now referencing an extra DLL for a circumstantial purpose. 3) P/Invoke into all the CreateAtx* stuff in Win32 API. (in fact, you can limit the scope of the activation context so that it's only active for the duration of "ShowDialog".) This documentation is very confusing though. This is not a detection problem in Microsoft.Win32. It's just a fit-and-finish bug that never got fixed. You might also have to make sure you aren't using a hook procedure (not sure if WPF does this "for you"). If you end up with exactly the dialog above except for correctly themed scrollbars and buttons, then this is what's happening. This happens because you’re pulling in the old version of comctl32.dll.

1) Add a manifest to your EXE that specifies version 6 of comctl32.dll.
2) Call System.Windows.Forms.Application.EnableVisualStyles. Downside is that you’re now referencing an extra DLL for a circumstantial purpose.
3) P/Invoke into all the CreateAtx* stuff in Win32 API. (in fact, you can limit the scope of the activation context so that it’s only active for the duration of “ShowDialog”.) This documentation is very confusing though.

This is not a detection problem in Microsoft.Win32. It’s just a fit-and-finish bug that never got fixed.

You might also have to make sure you aren’t using a hook procedure (not sure if WPF does this “for you”). If you end up with exactly the dialog above except for correctly themed scrollbars and buttons, then this is what’s happening.

]]>