Markus,

>>Will they have some type of transporter wizard, etc? Are the properties and methods of each model vastly different from each other, or is it as simple as "hacking the VCX or SCX" to point to a different form class and perhaps changing a property or two?
>
>It's a radical new approach. A paradigm shift. I would guess that there will be some sort of transport mechanism, but I would guess that it will work about as well as converting a FP/DOS form to Windows.

Thanks for the info. Now I understand the author's point a little better about having to start over.

>But at least if you use WinForms, you have the choice to approach it differently.

I'm sure there will be lots of mixed-mode apps during the transition to Avalon, as people try the approach you suggested of calling Avalon forms in the same app with or even from inside of WinForms. But, the developer will then have two radically different approaches and paradigms to deal with for quite a long time (assuming that the developer has a few WinForms apps to maintain).

I think Microsoft probably should have put more effort into backwards compatibility, but as in the consulting business, change is usually good for business. Shifting the paradigm too often, however, can lead to dev burnout or rebellion -- I wonder if they will be surprised at the flak they will take on this.