ADO.NET now or LINQ later

[Cornjerker]

I've been resisting learning ADO.NET. I can pound out regular ADO
solutions really quick and I haven't hit the breakingpoint that should
force me to switch. Now I've seen a new data solution in the next
revision of VB call LINQ. Should I take the time to learn ADO.NET now
or wait for LINQ. Keep in mind I haven't needed ADO.NET yet. Will
LINQ take the place of ADO.NET?

Thanks for your thoughts,
C

 

[Guest]

Hi,

Linq is a preview of a technology that is planned for next version of
visual basic that is useful for querying xml, objects, and data from a
database. It way to early to speculate if what its final version will be
like.

Ken

 

[agapeton]

ADO.NET is way too much work for anyone to justify doing. I can't
imagine a manager approving writing anything in that these days. Frans
Bouma did the world a huge favor when he wrote LLBLGen, a data
abstraction later for .NET.

www.llblgen.com

It's a $30,0000 peice of software for $300. You access all data
strongly typed, with full syntax coloring, compile time checking with
intellisense. You never have to look at the output code of it as is
the nature of abstraction laters...but the code is in C# or VB.NET. It
generates projects for both the legacy VS2003 and for the more
appropriate VS2005.

Seriously...forget ADO.NET. Learn LLBLGen now.

 

[Oenone]

ADO.NET is way too much work for anyone to justify doing.

It is?? It took a few days to learn ADO.NET. And it's great, much better
than ADO Classic. I can't comment on LLBLGen as I've never heard of nor seen
it, but ADO.NET has been just fine for everything I've needed it for -- and
as a developer of database applications, I've needed it for a lot of things.