>Bear in mind that WPF addresses two 'resizing' issues: not only the pixel adjustment based on monitor resolution but also the resizing of >individual controls (or groups of controls) when a window is re-sized.

If you are starting off with a known resolution and screen size the only time you need resizing is to expand the size of lists. Thats handled very well within the existing winforms via anchoring,dockng and the layout grids.

I think my point here is getting lost. The premise this thread started out with is WPF is WOW if you haven’t started using it you need to.
I’m saying No that’s not entirely true. There is a whole segment of application development on the windows platform that doesn’t need anything WPF offers and in fact it would be counterproductive.
There are millions of line of business applications out there that don’t need a single graphical enhancement. They don’t need pictures of users they don’t know next to their names or pictures of parts or any other graphic enchantments.

Are there applications that would greatly benfit from WPF? Sure. I think my point here is getting lost. The premise this thread started out with is WPF is WOW if you haven’t started using it you need to.
I’m saying No that’s not entirely true. There is a whole segment of application development on the windows platform that doesn’t need anything WPF offers and in fact it would be counterproductive.
There are millions of line of business applications out there that don’t need a single graphical enhancement. They don’t need pictures of users they don’t know next to their names or pictures of parts or any other graphic enchantments.

If your app is hitting the mass market or you have a lot of resizing or you can benefit from the latest wiz bang graphic layouts.

If your doing meat and Potatoes Line of business apps. No. Your just wasting your clients time and money.