Bonnie
Well, when the time comes a leader like you probably will want to rewrite your Winforms; I'd say the difference is sort of like 16bit vs 32bit development; the 16bit still works on the new OS but the new 32bit seems to offer so many advantages.
But this is still 3 years away, so if you must use dotNET for such work then the "STAY PRODUCTIVE" rule means Winforms are the only option.
The current "advice" seems to be that if you separate the UI from the data and business rules in the approved fashion, you should be able to write quick Avalon/XAML frontends when it comes to it. Not sure why this is used to encourage Winform development, though; one might equally apply this to using VB or even VFP in 2004 for fat client frontends, with SP or BO in behind. If you already have the business layer and/or depending how you create hooks into your new dotNET business layer, the latter might make a lot of sense.
Regards
j.R
"... They ne'er cared for us
yet: suffer us to famish, and their store-houses
crammed with grain; make edicts for usury, to
support usurers; repeal daily any wholesome act
established against the rich, and provide more
piercing statutes daily, to chain up and restrain
the poor. If the wars eat us not up, they will; and
there's all the love they bear us."
-- Shakespeare: Coriolanus, Act 1, scene 1
