LLBLGen Pro Example Using ASP.NET 2.0

Frans Bouma is the creator of the very popular LLBLGen Pro O/R mapper for .NET.  He just posted a nice walkthrough showing how to use the new version of LLBLGen (which includes some really nice new ASP.NET datasource controls for UI binding) to perform the same scenario I showed in my DLINQ post last weekend

You can step-through his sample here, and watch a video of him doing it live here.

June 10th Update: Ayende also wrote a blog post that also followed my steps using the .NET version of ActiveRecord.  You can read his post here.

One of the nice things about the LINQ project is that it decouples storage and data modelling semantics from the LINQ query semantics and language support.  What this means is that you'll be able to use LINQ to perform queries against multiple data-sources -- and any O/R implementation.  So you will be able to use the elegent and productive LINQ programming model with LLBGen Pro, NHibernate, WilsonORMapper, DLINQ, or any other O/R data model you want.  You can also use LINQ against your own objects/business classes like I showed in my first LINQ post here.

This provides developers with a tremendous amount of flexibility and knowledge re-use, and also provides O/R and data providers with great opportunities to innovate even further, and easily go after and target developers who understand the LINQ query language.

Hope this helps,

Scott

P.S. Paul Wilson posted a cool control on his blog a few weeks back that showed a nice ASP.NET datasource control that he built that allows you to easily databind ASP.NET controls against his WilsonORMapper.  You can read about it here.

P.P.S. Make sure to also check out the .netTiers templates for CodeSmith too. :-)

 

Published Friday, June 9, 2006 6:03 PM by ScottGu
Filed under: , , ,

Comments

# re: LLBLGen Pro Example Using ASP.NET 2.0

Saturday, June 10, 2006 1:03 AM by ScottGu
Hi Bobby,

Sorry about that -- I just added a link to yours as well. :-)

Thanks,

Scott

# re: LLBLGen Pro Example Using ASP.NET 2.0

Saturday, June 10, 2006 9:09 AM by OpenSource
Both tools are quite costly to someone who just wants to build solutions at home.  I could see a company buying these, but certainly I can't afford these tools at home.

I know this is a tad off topic, but this is one of the reasons I look forward to DLINQ tools within Studio.  Buying VS 2005 used up all my allowance  :)

I encourage both CodeSmith and LLBLGen to release tools to the 'hobbyist' at home at a reasonable price.  Who knows, after success at home, they might convince their boss to buy it at work...  :)

# re: LLBLGen Pro Example Using ASP.NET 2.0

Saturday, June 10, 2006 10:40 AM by OpenSource
Let me add - I'm really impressed with Paul Wilson's work.  The included dataobjectsource control is icing on the cake as far as I'm concerned!

# re: LLBLGen Pro Example Using ASP.NET 2.0

Saturday, June 10, 2006 7:17 PM by Sachin
Scott,

LINQ-DLINQ is/would be a single technology stack and hence the user experience would be much better than say LINQ-LLBLGen or LINQ-NHibernate.

I say this, because these products might not necessarily be complementary to each other.

NHibernate already has HQL; they'd be reinventing the wheel as far as incorporating LINQ is concerned.

LLBLGen does not have a pseudo-query language; if it does I haven't used it (its predicate construction mechanism is very nice).  So, this  would probably be a nice addition.

I think the user experience would be, at best, clunky.  I do hope Frans and the guys at NHibernate prove me wrong.

Sachin

# re: LLBLGen Pro Example Using ASP.NET 2.0

Sunday, June 11, 2006 12:45 AM by Sachin
Impressive.

Not sure about how LINQ would complement NHibernate, LLBLGen and other OR/M tools, though.  Time will tell, I suppose.

# re: LLBLGen Pro Example Using ASP.NET 2.0

Tuesday, December 26, 2006 3:40 PM by Eric Newton

@Sachin:

Sachin, LINQ isn't a replacement nor a complement to NHibernate/LLBLGen/WilsonORMapper.

LINQ is the ability to express the intent of a query in C# or VB.Net and allow the engine of NHibernate/LLBLGen/WilsonORMapper/DLINQ  to provide that data requested.

LINQ defines what the query wants and not how to do it... which is what is so cool about it.  In theory, defining what you want allows any of those mentioned OR Mappers to build SQL statements just like before.  

Remember, OR mapping is not just generating SQL statements... they are in charge of *managing* the object instances that represent the database rows.  Hence, "UPDATE this Object" actually produces an UPDATE in the db.