We are ready to start a brand new project at work, no legacy code. We did use Subsonic in the past and we pretty happy with it. But that was before Linq.
Has anyone had to face this same issue (Linq x Subsonic)?
What was your decision? What were the reasons?
Any insight appreciated.
We write our own datalayer or have it generated vs our datasource with a program we wrote. I'd be interested to know what benefits you get from using something like LINQ/Subsonic.
The one thing I love about LINQ, which I don't think SubSonic handles as gracefully, is automatically dealing with joins.
FROM a in db.Orders
where a.Total > 100
SELECT new {a.Item.Desc, a.Customer.Name};
will automatically generate SQL like thisL
select i.DESC, c.NAME
from ORDERS o
inner join ITEMS on o.ItemID = i.ItemID
inner join CUSTOMERS c on o.CustomerID = c.CUSTOMERID
where o.TOTAL > 100
SubSonic
Pros:
Cons:
Keep in mind:
Linq To SQL
Pros:
Cons:
Keep in mind:
Also evaluate the ADO.NET Entity Framework and here.
The biggest risk with linq to sql is that Microsoft will grow tired of it and abandon it. There is a lot of speculation that this has already happened and that only the entity framework will be updated. Subsonic does not suffer from this and worse case you have the source code to make your edits.
What about NHibernate? Is it really out of the picture for new projects? Still, people coming from Java will find it familiar and you can also use it with .NET 2.0 and Mono.
You might want to look into what happens when MS stops developing LINQ to SQL,as it appears to be happening. SubSonics latest version is easier to create queries and more readable, then their previous version.
My experience has been primary with SubSonic. It is very straight forward to deploy and you'll have your DAL completed in under a half hour. Bear in mind that this is a Swiss Army knife, as it is designed for utility. Basically you get a class generated per class, as well as the ability to peform lazy loading for collections. You can also execute stored procedures via the framework, so if you have complex data structures you can fetch them from the database and update a class that you hand craft.
I've used it on 5 major projects now, and am impressed with how quickly I became dependent on it.
I went with Linq because it's built into the framework. For those saying it will not be supported by Microsoft... it's LinqToSql that is going to be phased out. I believe one of the plans is to absorbe it into the Entity Framework.
I'm now using the Entity Framework. It also uses linq and basically it's exactly like linqToSql with more flexibility and power if you choose to use it.
I tend to avoid 3rd party frameworks and orms because eventually they die out as well. I believe they have more of a chance to die out because their life comes from how many people are interested in it and use it. Their life is also heavily dependent on it's main author/contributor.
Entity Framework offers significantly better performance than Subsonic:
http://www.timacheson.com/Blog/2009/jun/entity_framework_vs_subsonic