>I'd be more concerned about MS deciding that compiling VFP in .NET violates the EULA.
>

1. MS doesn't own the language per se, so as long as VFP internals are not used and the product name doesn't have trademarks in it, I don't think MS could do much if anything to stop it

2. The more people jump on the .NET bandwagon the better it is for MS's bottom line in the long run. Evidence MS's enthusiastic support for Iron Python. Need I say more?


>
>>>You're right on the name, of course.
>>>
>>>FP1.0 was the turning point, however, in FoxPro becoming its own product. True, you needed something like Scrimage. Remember that one? Russ Freeland was a really helpful guy to the Fox community. And it was the READ EVENT that allows us have multiple windows active without having to manage them was added: Tom Rettig on the beta forum had been making the case, and that afternoon Janet Walker sat down with Dave Fulton (from what was recounted short thereafter), and the next morning we had a build with READ EVENTS in. Or as it was called at the time (when the first Iraq war was in everyone's mind), the MOAR -- the Mother Of All Reads. Those were heady, exciting days.
>>>
>>>Those were also the days when there would be 400 new messages a day on FoxForum. I'd be up until 2 am reading reading them, learning from them. It was exciting. As it is now: what we will have from eTecnologia's effort is the best of both worlds. As Pertti notes, it is working. The parts that need yet to be done are not the difficult parts (well, there are likely a couple of difficult parts left, but the difficulty of making a real .Net DLL and EXE out of VFP code has been solved). The extensions they have created (for example, the ability to strong-type of variable, as in TLOCAL lcString as String, and get increased speed for processes that require it, are simple and to-the-point. It's optional, of course: in almost all cases, the increase in runtime speed would be irrelevant. That's why I find this time just as exciting, because of the possibilities it is opening up.
>>>
>>>I am taking all bets for Venti Latte's (even odds, although I should be giving 3:1 at least) that by this time next year (24FEB2010) the eTecnologia compiler will be at 98% compatibility. When those taking me up on the bet have to pay up, I'd appreciate payment in gift cards to Berea Coffee and Tea (http://www.bcandtco.com), as I'd have to drive to a Starbucks, and this place is on my way after I work out. <s> But if Starbucks is easier, I can always give them to the kids. Come on folks, put your latte's where you mouth is ... well, I guess that's what one does with a latte' anyway, right?
>>
>>ONE YEAR!
>>
>>So many things could happen in a year. MS seeing that VFP would be able to get in the .net sandbox could make an announcement that they will shortly launch something to replace .net
>>
>>I don't know but they seem pretty serious to really wipe out VFP for good ;-)