Hi Alex,

Of course I'm not interested in loosing all I love in VFP. If I was not clear enough (perhaps I wasn't) when I said "without loosing it's IDE" I meant ALL those goods we can have while in the command window.

Also, I (strongly) don't want to loose it's data engine (99,99% of my apps are dbf oriented). If the price to be a part ot .net is to loose all that, thanks, I'll stay with the current version.


>Why would the resulting hybrid be any different than VB .Net?

For the same reason that Delphi (in the net framework) will be different from VB.net (that's what I've been told).

>What would be the point?

Think it could be a way to position VFP in the frontline of developing tools, whatever that means, but IT goes a lot like the fashion industry, and now .net, C# is fashion etc (I know that'll be bombed for saying this, but that's ok), get some extra marketing, some folks that are thinking about leaving VFP could get extra motivation to stay with it, and the like. To me it makes no difference.

The purpose of my message was not to make a proposition, rather a simple questioning, look at the "?" at the end of the message title :)

Regards,

Fernando