>That’s a pretty broad statement with very little meat to back it up.
>WPF s an attempt to fill a need that simply doesn’t exist in line of business applications. We have no need of a platform that allows graphic designers to paint up forms or controls . Most line of business applications I’ve worked on since win 3.0 don’t even stray from the standard controls. A typical Business form is pretty straight forward. You have a list of some type or search criteria and a details section or page. The details will have some validations and maybe some custom formatting. If you work in a team or have been coding for a while you probably already have base class forms to handle some or most of the query and crud logic on your business objects. So that just leaves dropping controls on the form wiring up the data binding. The majority of the data binding is usually a simple matter of putting the field name in a binding property, pretty fast and straight forward. Any validation are equally fast and straight forward. Go to the property sheet click the events button choose the valid event and dbl click to get your stub. Call your business rule or write your valid code. Again Fast and straight forward
>The users will be presented with exactly what they need exactly how they need it. And guess what else none of it will require a 3D graphics card. That’s fairly improtant in an organization with thousands of workstations.
>We don’t need yet another MS markup wana b language (AXML) for that . Just the fact that you have to go into the axml file and hand code things precludes it be more productive than WInforms.
>
>Now I’ve pointed out why I don’t see value in wpf in a line of business application. Can you show me where there is a value?

It's XAML, not AXML, which may be an indication of the depth of your understanding.

Don't get me wrong, I am not a bleeding edge guy. But if you are honest with yourself you will recognize that what you are describing is your own experience, not trends going forward.