That is what I'm wondering at the moment. Due to the nature of C programmers, if it wasn't purposely left open to let them write their own wrappers around LINQ so they can reference the technology however they see fit.

This vs. VB programmers who don't want to be bothered with the details and just want a RAD tool.

I start a C# class next week. I plan on asking the teacher if they plan to cover this topic in a new class that starts in Dec. on handling data. They have a C# and VB version.

>Craig,
>
>>There's also an issue of me dev team...mostly C++ developers. Will it make sense for some of us to use VB and others C#? In .Net it really doesn't matter, but it might from a staffing/maintenance/enhancement scenario.
>
>If you and enough other C#-ers scream loud enough and long enough, maybe Anders can be convinced to simplify the gobble-de-gook syntax before release. (I am just imagining the feedback he'll be getting from people who DO understand data but have chosen C# -- just as I can imagine the groans from those same people when they compare the C# approach to VB.)
>
>I heard one VFP-oriented developer say that it may be just easier to set up classes to talk directly to the LINQ framework instead of using the C# language extensions.
>
>It's pretty obvious which team has been most influenced by Yag.