>Srdjan, it was possible to bring a FPW app into VFP and make it run, but it didn't use all the new UI features that users expect from a 32-bit app and it didn't work as well with remote data as it should.
>
>Similarly, a NET app written in 2003 using untyped datasets and Winforms will still run bit it won't offer the cool features of xaml or Silverlight and the app will just be crying out to be rewritten for the EF.
>
>That's the joy and hurt of NET IMHO: MS keeps introducing really excellent new features that are too good to let pass by... meaning there must be incredible pressure to keep tweaking existing code to keep it up-to-date. Which is why I would have thought that the idea of a 4GL that compiles the same form to winform for those who need it, xaml for those who need it and Silverlight2.0 for those who need it and compiles to use the latest greatest data techniques as well, should be exciting to everybody here.

Ok that is the same situation was in VFP world as well, over past 15 years. You could run your old-timer relatively well, but everybody else would be driving brand new car - so you are compelled to change as well.
But If understand correctly your point; That would be eT turning VFP/xBase development paradigm into sort of higher level
markup-language, that later translates into whatever is latest and greatest - NET assemblies wise .

That kind of situation would be actually ideal ! NET platform itself has no better place to go, but building some sort of 4GL tower
on top of this wasteland/ocean of various assemblies, classes and frameworks. Imaggine eT being bought up by M$, if they do succeed in this direction few years from now. I would loooove to see this 'deja-vue' happen;

New VFP would in that case re-surface onder some stylish code-name much earlier then I predicted {g}.
I am sure young NET developers will love it ;)

Cheers :)