>>>Obviously I did not read Hank's link closely enough the first time. I did not catch who Scott Barnes was.If a former Silverlight product manager says Silverlight and WPF are doomed within Microsoft, I have to acknowledge it's at least a possibility. Just what I need as an aspiring .NET developer. The thing is so huge and constantly changing it's enough of a challenge to begin with. I don't want to have to worry about Microsoft junking core components over internal politics. Who wants to invest time learning something that may be killed off? As it happens I have a Silverlight book on order from Amazon.
>>
>>http://www.riagenic.com/archives/358
>>http://newteevee.com/2010/09/16/in-flash-html5-battle-silverlight-is-the-big-loser/
>>
>>If WPF is somewhere between lame and dead duck there will be a way to move your concepts - I have here a demo of running vfp scx-based form in Winform and partially in WPF with most of the needed properties and some events linked. If you have clearly separated tiers, you don't have to fear the sky is falling... And even if the sky is falling, that might be interesting [veg]
>>
>
>One of the technologies I have been trying to learn is ASP.NET MVC. Have been a fan of three tiered architecture since FoxExpresse. Hopefully our friends in Redmond don't dump MVC as well.

Over a year ago there were many MVC, MVP, MVVM discussions here. The more commonly used architecture is MVVM , but it's good to be familiar with them all (if you want to be marketable).

A nice graphic here:
http://visualizationtools.net/default/wpf-patterns-mvc-mvp-or-mvvm-or/

There is a MVVM model for Silverlight:
A little old (Silverlight 2):
http://msdn.microsoft.com/en-us/magazine/dd458800.aspx

Jesse Liberty video:
http://www.silverlight.net/learn/videos/silverlight-4-videos/mvvm-introduction/

A nice graphical comparison of them:
http://nirajrules.wordpress.com/2009/07/18/mvc-vs-mvp-vs-mvvm/