There are many, many excellent C# developers who were using winforms in their previous employment and their old employer was not interested in even looking at WPF. For whatever reason, those folks were out of a job when the company downsized and are now working for companies who are moving their winforms apps to WPF so they are scrambling to catch up. The point is to keep yourself marketable. You might not like it, and you may even despise MSFT for it, but it is a reality all too many are dealing with now.


>And there are still many people out there making a decent living supporting them. Just because MS speaks doesn't mean everyone's going to run to their local, MS supported, college and retrain.
>
>If I even hinted to my boss that we retool all of our apps because of WPF, he'd laugh me right out of the office. We have WAY too much work to do to play with something new. And WinForms & Web apps are working fine for us, and will continue to do so for a long time.
>
>
>
>
>>Many major enterprise apps were built with VB 6 (and below). That didn't stop MS from stopping supporting it and going forward with .NET.
>>
>>>Yes I do. You're saying that WinForms will go the way of VFP, and I completely 100% disagree wiith you.
>>>
>>>There are so many companies out there with major enterprise level apps in use that have no reason whatsoever to incorporate WPF or be web apps. Again, if what Paul Sherriff said in CoDe magazine that "MS won't update WinForms" is true, then MS truly has lost focus with their customer base. That's a major bad decions IMHO.