Linq adoption

  • Thread starter Thread starter ryanbaldwin
  • Start date Start date
R

ryanbaldwin

pre-emptive apology: I'm not sure if this is the best place to post
about Linq, but I haven't seen a public linq forum, so I figured
ado.net would be the closest thing. My apologies if my assertions have
failed.

Here's the deal: We are just starting work on 2 new applications that
aren't scheduled for release until the end of Q1 2007 at the *very*
earliest (pipe-dream date). The big question that I have, given that I
loath ado.net and love object-persistent frameworks, would it be unwise
(and if so, how much so) to start using Linq for for db interaction
using the preview released in May '06?

We understand the risk involved in doing so from a framework
development point of view (it's still being developed, interfaces may
change, etc), but are still interested in its adoption. I've started
playing around with Linq at home on a small pet project, and from what
I've experienced (which isn't saying much) it seems stable for the
basic functionality we currently desire (basic CRUD work and execution
of sprocs).

Thoughts? Is it still too early to be an early adopter? Should I
continue working on my own small object persistent framework for our
app? Is there *any* RTM date (or approximation) for linq/C# 3.0/VS
2007? Does Linq have some massive, glaring bugs that i haven't noticed
yet (huge memory leaks, for example)? Is there any schedule as to when
the next CTP release (or beta/RC) is due?

Any input would be appreciated - as we're simply trying to weigh our
decisions.

Thanks.
 
Hi there,

This is the ?Linq forum:
http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=123&SiteID=1
I think you are talking about DLinq the ORM with Linq queries - an excellent
combination. (Yes, I am a DLinq, Linq fan).
The problem here is that DLinq is far from finished as it is in an early
phase. A lot can change before it is RTMed.
Thus I would recommend against using DLinq now as it is too early for
serious work. I think it is better to pick one of the reliable and working
3rd party ORM out there such as LLBLGen, XPO, ... They don't do queries in
such an elegant way, but they are great. And once Linq is released I they
will implement it.
Of course, once (D)Linq it gets a go-live license I would jump asap on the
Linq wagon in one or the other way- no doubts about that.
 
Yes, I should have been more specific - DLinq is the Linq technology I
was referring to. It's so hard to resist using it after getting the
taste. Curses MS for allowing us to taste test the meth of data
access! Instantly addicted I am.

I'll have to check out the other ORM components you've listed. I
checked out NHibernate but it seems wonky for .NET 2.0.

Thanks for the reply.
 
cranley said:
Yes, I should have been more specific - DLinq is the Linq technology I
was referring to. It's so hard to resist using it after getting the
taste. Curses MS for allowing us to taste test the meth of data
access! Instantly addicted I am.
Click to expand...

I understand the feeling :-)
 
Back
Top