Kevin,
>I know you've said this several times. And I'm being sincere when I say that I just don't "get" how LINQ to SQL feels like .NET has moved closer to VFP. (IMO, LINQ to SQL is the weak "link", no pun intended, of LINQ).
>
>I like LINQ in general - specifically the fact that I can use similar syntax to query different types of objects. But I don't see the connection to VFP. Different strokes for different folks, I guess...
(sorry, I am joining this way late...)
The two main parts of LINQ I see as being "VFP-like" are:
-- LINQ seems more "inline", like SELECT statements directly in VFP code.
-- LINQ gets that much closer to the idea of creating a "cursor from a cursor" that I love so much about Foxpro. I know there are other ways to emulate that behavior in ADO.NET, but LINQ seems a LOT closer to the idea of gathering data from disparate data sources and then combining them in different ways for a final result. If the performance is there, that is going to be a huge boon (in my opinion).
If those two points aren't important, then what exactly are folks wanting to be VFPish in .NET and not getting? I am not a C# guru or ADO.NET expert by any means (yet), but it seems to do pretty darn well. What is it missing other than things simply being _different_?
Thanks,
JoeK
Previous
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only