Pedantic: From the job posting that a sibling comment linked, the display tech appears to be under OSG. That means it's actually under Terry Myerson, not Scott Guthrie.
I have a few WPF 4 bugs that were marked "fix in next version" 3-4 years ago, and then it was announced that there is no next version - i'm in the process of moving off WPF and this newfound love is not going to change anything.
Similar problem with IE for me. I raised a case with gold partner support when IE9 came out as it broke ClickOnce download prompting. Been bouncing back and forth between framework and IE teams ever since.
Result: we now have to ship a .reg file to our clients before we can launch our shit via ClickOnce. That's only 2000 people we now have to hand hold through this.....
Although I sort of understand why, it's a shame - WPF cross-platform would be very awesome, and mono still has no plans to implement any of it, last I heard. Windows forms is just too ancient.
XAML != WPF. XAML is a language for object instantiation, thats it. Similar to XIBs in the Apple world.
There are no less than 3 similar but different and incompatible UI libraries that can be instantiated by XAML: WPF, Silverlight (WPF/e), and Windows store/phone (WinRT). WPF is dead like WinForms but the only solution for normal windows apps unless somethings changed with WinRT to make non full screen apps with.
If you have ever tried to develop across more than one of these with a shared code base you will know how frustratingly similar yet how incompatible and different they are. They are not supersets or subsets they are forks.
WPF is more or less owned by the Windows team. This is all stuff under Scott Guthrie's control
Pedantic: From the job posting that a sibling comment linked, the display tech appears to be under OSG. That means it's actually under Terry Myerson, not Scott Guthrie.
WPF just got some love a few minutes ago - they've got plans for a new release of it by the sound of things.
I have a few WPF 4 bugs that were marked "fix in next version" 3-4 years ago, and then it was announced that there is no next version - i'm in the process of moving off WPF and this newfound love is not going to change anything.
Yes. Good luck to Microsoft trying to be relevant in HTML5 space.
Similar problem with IE for me. I raised a case with gold partner support when IE9 came out as it broke ClickOnce download prompting. Been bouncing back and forth between framework and IE teams ever since.
Result: we now have to ship a .reg file to our clients before we can launch our shit via ClickOnce. That's only 2000 people we now have to hand hold through this.....
8 replies →
WPF is alive and kicking. I'll just leave this here... https://careers.microsoft.com/jobdetails.aspx?jid=137020&pp=...
Although I sort of understand why, it's a shame - WPF cross-platform would be very awesome, and mono still has no plans to implement any of it, last I heard. Windows forms is just too ancient.
I thought WPF was killed during the whole mess of killing Silverlight, etc. a few years back?
No WPF is still there. XAML is still the basis for windows store apps, and windows phone apps.
XAML != WPF. XAML is a language for object instantiation, thats it. Similar to XIBs in the Apple world.
There are no less than 3 similar but different and incompatible UI libraries that can be instantiated by XAML: WPF, Silverlight (WPF/e), and Windows store/phone (WinRT). WPF is dead like WinForms but the only solution for normal windows apps unless somethings changed with WinRT to make non full screen apps with.
If you have ever tried to develop across more than one of these with a shared code base you will know how frustratingly similar yet how incompatible and different they are. They are not supersets or subsets they are forks.
3 replies →
One of two basis for Windows Store.
WinJS is the other.