LINQ - and the future of OR mappers?
Joined: 01-Jul-2005
Ren wrote:
Here is a link to a rather amazing video of Anders Hejlsberg talking about the future of t LINQ.
It seems that the possiblities of this are pretty amazing. The ability to use a single unified programming model across domains is a jaw dropper.
What is the future of OR mapping products like LLBL and others with the release of this on the horizon?
One thing we're planning now is LLinq, which is the LLBLGen Pro core controlled in code through Linq constructs. This is possible because Linq defines a structure of elements which can directly be used by an underlying library 
.
The other things we're planning have relations to that, but I'll leave it at that for now . Linq is cool stuff, it will truly make o/r mapping a first class citizen
Joined: 31-Jan-2005
Otis wrote:
Ren wrote:
Here is a link to a rather amazing video of Anders Hejlsberg talking about the future of t LINQ.
It seems that the possiblities of this are pretty amazing. The ability to use a single unified programming model across domains is a jaw dropper.
What is the future of OR mapping products like LLBL and others with the release of this on the horizon?
One thing we're planning now is LLinq, which is the LLBLGen Pro core controlled in code through Linq constructs. This is possible because Linq defines a structure of elements which can directly be used by an underlying library
The other things we're planning have relations to that, but I'll leave it at that for now
Very interesting stuff. Seems like DLinq is trying to be an O/R Mapper as well. Did I hear him right saying that DLinq is the ADO of the future? Does that mean SqlDataSources will go away? Or the coming LLBLGenDataSource?