Mike,

>I sure wish you hadn't said anything about VFP-like data binding. To me, on my maiden .NET project, it seems like anything but. In VFP the act of binding a control to a database field was duck soup. It was just a matter of setting the ControlSource property. Oho, not in .NET. They make you jump through hoops and sing Jingle Bells every Christmas.<

I dunno about that ... even in VS2003 (with which I'm more familiar at the moment), databinding to a column in a DataTable was not as difficult as you make it sound.

this.MyTextBox.DataBindings.Add("Text", MyDataTable, "MyColumn");

How hard is that?

~~Bonnie




>>>Hi.
>>>I've been reading a bit about the next version of C# (3.0) which will incorporate LINQ (Langauge Integrated Query) features.
>>>It would appear to me that a lot of the stuff they are goin to be putting into C# 3.0 is nearly directly taken from functionality that is alredy in VFP, and after this version, in fact Dot net will have almost everthing that VFP has.
>>>
>>>So I am just psing the question if :
>>>C# 3.0 = VFP 10 or indeed if VFP 10 = C# 3.0
>>
>>C# and VB relate to releases of Visual Studio, nothing to do with VFP directly. Starting with VS 2005 which contains many VFP like data-binding and other VFP-like features, Microsoft continues to leverage useful data-centric functionality and extensiblity features from VFP for future versions of VB, C#, and the VS IDE shell.
>>
>>LINQ is not C# only, it will be surfaced in VB as well and the VB version will probably look much more like VFP code. See http://msdn.microsoft.com/vbasic/future/.
>>
>>There are some developers who worked on VFP who are now working on LINQ and other VB/C# enhancements to help bring more VFP-like functionality to .NET programming in the future. Ocras, the next version of Visual Studio that will contain the new LINQ features in VB and C# plus more, is scheduled for release sometime in 2007. The version of Visual Studio beyond Orcas will continue to add more data-centric and data-programming features to VB and C#.
>>
>>The VFP Roadmap describes how VFP will be updated http://msdn.microsoft.com/vfoxpro/Roadmap/default.aspx.
>
>
>I sure wish you hadn't said anything about VFP-like data binding. To me, on my maiden .NET project, it seems like anything but. In VFP the act of binding a control to a database field was duck soup. It was just a matter of setting the ControlSource property. Oho, not in .NET. They make you jump through hoops and sing Jingle Bells every Christmas.
>
>More amazing yet, this so-called ease of use is being trumpeted by the marketeers as a selling point. Step up, step right up, watch the amazing Rocket Boy bind a control to a database field....