Basically Linq to NHibernate is now working only off the trunk (last I checked) which is fine, however as beta 1 broke the previous stable Linq bits, it’s not a simple answer as to ‘what do I want to commit to if not the moving trunk code base’.

More soon. A lot more…

Damon

Thank you!

I’ll actually then ask Ayende if I can be a distribution point for perhaps builds he says are stable (and immediately I’ll list the new location). I just had to figure this out myself and I remember when he moved it from his experiments directory to NHContrib but I didn’t know it was not there..

I would say he is working on what could be the single most critical software component for getting .NET to not just keep up but finally take a small lead for a moment in time over our Java peers.

For us Linq (and really the functional language aspects of Expressions and the fantastic enhancements on delegates with Lambada Expressions) was a stroke of genious for Microsoft started way back with the List and foreach, find, etc…

We are obsessed with writing providers and indeed are writing up some abstractions to make it easier to manipulate the Expression tree.

For us it’s not just about ‘Linq to Data Source X’ but ‘Linq to Domain’ where domain is specific to an organization and is abstracting perhaps ten data sources… THAT is amazing for SOA where the API is all about say structured finance but it’s calling into WCF, MSMQ, MQSeries, etc. without any ‘technical’ API pollution.

Thoughts?

Get you that in a bit.

Thanks,
Damon

Any ideas?

Thank you - and great post/site!