>Markus,
>
>>>And if you're developing a Windows GUI app today using Microsoft's "official" latest-and-greatest Windows programming environment, WinForms, you're going to have to start over again in two years to support Longhorn and Avalon. Which explains why WinForms is completely stillborn. Hope you haven't invested too much in it.
>
>>Avalon objects can be used in addition to WinForms objects. For instance, the following is possible:
>>WinForms is by far the best way to get ready for Avalon, for this very reason.
>
>In the context of the original post (see above), the more interesting question relates to porting WinForms-based apps to completely Avalon-based apps. IOW, if you want your existing WinForms app to no longer use WinForms, but use Avalon forms only, how do you accomplish that?
>
>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.

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

Markus