I know that early talk about this indicated that Linq would still be a
major component, even after EF comes into its own. But some articles
that mention that programmers are irritated that they've spent time
learning Linq, when it has now become an essentially obsolete
technology. I've even seen contradictory statements about this within
a couple paragraphs.

Any opinions from those who have worked with both? What is the
compelling reason to continue using/learning Linq?

"Eric" <Eric at (no spam) ---nospam---.com> wrote in message
news:adp1d5d43dglrni2sqb0pj68lvjoggkfvj at (no spam) 4ax.com...
I know that early talk about this indicated that Linq would still be a
major component, even after EF comes into its own. But some articles
that mention that programmers are irritated that they've spent time
learning Linq, when it has now become an essentially obsolete
technology. I've even seen contradictory statements about this within
a couple paragraphs.

Any opinions from those who have worked with both? What is the
compelling reason to continue using/learning Linq?

Don't know for sure, but because LinQ isn't just about Linq To SQL, and can
be used with data in all forms, doesn't that mean it will be useful in areas
where EF doesn't touch?

-Scott

I know that early talk about this indicated that Linq would still be a
major component, even after EF comes into its own. But some articles
that mention that programmers are irritated that they've spent time
learning Linq, when it has now become an essentially obsolete
technology. I've even seen contradictory statements about this within
a couple paragraphs.

Any opinions from those who have worked with both? What is the
compelling reason to continue using/learning Linq?

I know that early talk about this indicated that Linq would still be a
major component, even after EF comes into its own. But some articles
that mention that programmers are irritated that they've spent time
learning Linq, when it has now become an essentially obsolete
technology. I've even seen contradictory statements about this within
a couple paragraphs.

Any opinions from those who have worked with both? What is the
compelling reason to continue using/learning Linq?

"Eric" <Eric at (no spam) ---nospam---.com> wrote in message
news:adp1d5d43dglrni2sqb0pj68lvjoggkfvj at (no spam) 4ax.com...

I know that early talk about this indicated that Linq would still be a
major component, even after EF comes into its own. But some articles
that mention that programmers are irritated that they've spent time
learning Linq, when it has now become an essentially obsolete
technology. I've even seen contradictory statements about this within
a couple paragraphs.

Any opinions from those who have worked with both? What is the
compelling reason to continue using/learning Linq?

I think you're imagining that Linq is just Linq to SQL...

I use Linq all the time, but hardly ever with ADO.NET objects. It really
comes into its own when used with object models such as ActiveDirectory and
Exchange where it is, IMO, little short of revolutionary...

On Sat, 10 Oct 2009 19:25:37 -0400, "Scott M." <s-mar at (no spam) nospam.nospam
wrote:


"Eric" <Eric at (no spam) ---nospam---.com> wrote in message
news:adp1d5d43dglrni2sqb0pj68lvjoggkfvj at (no spam) 4ax.com...
I know that early talk about this indicated that Linq would still be a
major component, even after EF comes into its own. But some articles
that mention that programmers are irritated that they've spent time
learning Linq, when it has now become an essentially obsolete
technology. I've even seen contradictory statements about this within
a couple paragraphs.

Any opinions from those who have worked with both? What is the
compelling reason to continue using/learning Linq?

Don't know for sure, but because LinQ isn't just about Linq To SQL, and
can
be used with data in all forms, doesn't that mean it will be useful in
areas
where EF doesn't touch?

-Scott

EF is supposed to be adapted to work on XML files, and presumably
other areas currently covered by Linq. So I'm not sure that Linq will
continue to have its own domain there.

But of course there's "Linq to Entities" that serves the same purpose
as SQL for EF. Not sure if that's reason enough to keep up with Linq,
or whether I should just start concentrating on EF instead.

Thanks for the replies. I haven't done any work with ActiveDirectory
or Exchange, but I understand that EF will soon be incorporated as
interface to XML and other 'objects' (as of VS2010).