NewsBot
1
As you may know, I previously created replacement FileDialog classes for .Net 2.0 that allowed application to use Windows Vista style file dialogs, unlike the built-in classes which would always use the old-style dialogs even when running on Vista.
So you can understand that I was happy when I noticed that in .Net 2.0 SP1, System.Windows.Forms.OpenFileDialog and SaveFileDialog automatically use the new dialogs, so my work-around is now unnecessary.
But I was surprised to see that the same update was not made in .Net 3.0 SP1 for Microsoft.Win32.OpenFileDialog (and SaveFileDialog), which are meant to be used with WPF. So WPF applications still get old-style file dialogs on Vista, which is strange because WPF is meant to deliver a first-class Vista experience, isn't it?
So now I'm using System.Windows.Forms.OpenFileDialog in my WPF applications. It works, but it feels dirty.
Can anybody explain why this inconsistency exists? Or did they simply forget to update that class?
More...
View All Our Microsoft Related Feeds
So you can understand that I was happy when I noticed that in .Net 2.0 SP1, System.Windows.Forms.OpenFileDialog and SaveFileDialog automatically use the new dialogs, so my work-around is now unnecessary.
But I was surprised to see that the same update was not made in .Net 3.0 SP1 for Microsoft.Win32.OpenFileDialog (and SaveFileDialog), which are meant to be used with WPF. So WPF applications still get old-style file dialogs on Vista, which is strange because WPF is meant to deliver a first-class Vista experience, isn't it?
So now I'm using System.Windows.Forms.OpenFileDialog in my WPF applications. It works, but it feels dirty.
Can anybody explain why this inconsistency exists? Or did they simply forget to update that class?
More...
View All Our Microsoft Related Feeds