Seems the project is not active anymore. Or am I missing something? Is there any other unitorwork/repository implementations for nhibernate?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Seems the project is not active anymore. Or am I missing something? Is there any other unitorwork/repository implementations for nhibernate?
As Craig said, Ayende is pretty much against the repository pattern (and by extension somewhat, the unit of work pattern) now. See:
And there are plenty more where that lot came from.
The basic underlying premise is, he believes that NHibernate is already enough of an abstraction over the database so you don’t need another layer. On top of that, by abstract NHibernate, you’re doing yourself a diservice with regard to the powerful features that NHibernate provides.
Based on this new attitude, I would imagine that the repository and unit of work stuff in Rhino will be left alone now.