Linked by Adam S on Thu 19th Jun 2008 14:47 UTC, submitted by M-Saunders
Thread beginning with comment 319198
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: Comment by satan666
by TLZ_ on Thu 19th Jun 2008 19:07
in reply to "RE[4]: Comment by satan666"
You're underestimating how conservative businesses can be.
We're I'm working they're still using .NET 2.0 and probably will for a good while.
The only thing they've found interesting about WPF is Silverlight, which they decided to not delve into until a couple of years.
You're partly right of course, but it's better than nothing, eh?
RE[6]: Comment by satan666
by evangs on Thu 19th Jun 2008 19:18
in reply to "RE[5]: Comment by satan666"
Believe me, I'm familiar with how conservative businesses are. The company I work for still has me coding in C++ using ATL/WTL and Win32. It's just slightly surprising for me to see that Winforms were deprecated before we even began to evaluate it seriously.
That of course makes us wonder how long WPF will be around for before it too gets deprecated.




Member since:
2005-07-07
The sad thing is that just as the Mono team come up with a fairly usable implementation of Winforms, Microsoft deprecates it and starts pushing WPF. I'm not saying that the two are linked, but seeing as they are always going to be playing catch-up with the latest and greatest from Redmond, it is going to find very limited use.