>heard a lot of good things about LINQ but haven't checked it personally. And my personal position this early is that it will not be similar to how we do DM in VFP. So far, VS2005 + MM.Net can do the job for me as far as data manipulation is concerned.
>
>Now imagine if somebody said that about VFP- "I've heard stuff about the latest tools but haven't looked, and what I'm using right now does the job for me..." what would you say to them? ;-)

It's a different scenario because if VFP's future wasn't became bleak since the released of VS.Net, I will not look for the stuff no matter how good the promises are. The LINQ stuff is a bonus to what VS2005 offers.

>
>You may argue that your current work is not rendered obsolete by Linq. My response is "we'll see". Our C# code written in 2004/5 still works but is profoundly obsolete, to the point that it's difficult to support: everybody who looks at it wants to start over using latest coolest techniques.

It's sad to hear that you jumped into the .NET bandwagon that early. We only started releasing .NET versions of our apps with VS2005.

>IMHO features like the lambda stuff in Linq will have the same effect on your ADO.NET code. I'm supposing that you're not just entering and displaying data, you're adding value, right?

If LINQ features have huge advantages over what I do now with ADO.NET code but if the latter is already effective and efficient to do the job, maybe I will apply the LINQ only with future modules. Transition period would play here.