>>>>>>>>>>>>>
I don't know whether anyone else particpated in the web conference yesterday on PlaceWare called: "Microsoft .NET: The Next Generation Internet" put on by Microsoft. It was moderately informative with a overview of the .NET initiative. Not once was Visual FoxPro mentioned (not unusual for Microsoft). But in the question and answer period after the presentation, I asked; why is Visual Foxpro not included in the Common Runtime Library when all of the other .NET languages are (and according to Microsoft 30 other third party languages like Cobol are). They specifically stated they have no plans to make this happen and would only do so if a stong business case was presented to them. Sounds like a job for us and Robert Green.
>>>>>>>>>>>>>
Neil:
Don't run so fast towards VFP participating in the CLR. That is a hot topic beng discussed lately. Robert Green said at Devcon Miami that it was up to us if we wanted it.
There are many trade-offs in the CLR and not all of us are ready to give up VFP.
For starters, you could check out the following:
Jim Booth's article "The sky is falling":
http://www.advisor.com/Articles.nsf/aid/BOOTJ06and his recent chat in the UT:
http://fox.wikis.com/wc.dll?Wiki~WhatDoesDotNETMeanToTheVFPDeveloper~VFPhttp://fox.wikis.com/wc.dll?Wiki~CategoryDotNet
