Comments on: The Case for NHibernate http://www.sullivansoftdev.com/blog/2009/08/23/the-case-for-nhibernate/ From one geek to another Thu, 29 Sep 2011 13:47:33 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Brian http://www.sullivansoftdev.com/blog/2009/08/23/the-case-for-nhibernate/comment-page-1/#comment-338 Brian Tue, 23 Feb 2010 15:28:48 +0000 http://www.sullivansoftdev.com/blog/?p=124#comment-338 Thanks, XelHa! Glad I could help! Thanks, XelHa! Glad I could help!

]]> By: XelHa http://www.sullivansoftdev.com/blog/2009/08/23/the-case-for-nhibernate/comment-page-1/#comment-337 XelHa Tue, 23 Feb 2010 04:33:52 +0000 http://www.sullivansoftdev.com/blog/?p=124#comment-337 Hi Brian, I really appreciated your article, it's clear and concise, and I think you convinced me to use NHibernate. I was reading other articles about this topic, and yours is the most complete and to the point. Thanks and Congratulations. Hi Brian, I really appreciated your article, it’s clear and concise, and I think you convinced me to use NHibernate.

I was reading other articles about this topic, and yours is the most complete and to the point.

Thanks and Congratulations.

]]> By: Brian http://www.sullivansoftdev.com/blog/2009/08/23/the-case-for-nhibernate/comment-page-1/#comment-158 Brian Wed, 02 Sep 2009 16:48:42 +0000 http://www.sullivansoftdev.com/blog/?p=124#comment-158 @SeeSharpGears - If I'm understanding your idea correctly, I think it may already have been solved by Fluent NHibernate. Based on a set of conventions (either ones you define yourself or the ones that get used by default), properties can be mapped without writing explicit mapping files. You might check out the wiki section on auto-mapping here: <a href="http://wiki.fluentnhibernate.org/Auto_mapping" rel="nofollow">http://wiki.fluentnhibernate.org/Auto_mapping</a>. If you do decide to go ahead and do it yourself, you might want to be aware of some of the "gotchas" of implementing your own DAL, addressed by Davy Brion <a href="http://davybrion.com/blog/2009/08/build-your-own-data-access-layer-series/" rel="nofollow">here</a>, and Ayende Rahien <a href="http://ayende.com/Blog/archive/2009/08/24/a-guide-into-orm-implementation-challenges-reasoning.aspx" rel="nofollow">here</a>. Best of luck! @SeeSharpGears – If I’m understanding your idea correctly, I think it may already have been solved by Fluent NHibernate. Based on a set of conventions (either ones you define yourself or the ones that get used by default), properties can be mapped without writing explicit mapping files. You might check out the wiki section on auto-mapping here: http://wiki.fluentnhibernate.org/Auto_mapping. If you do decide to go ahead and do it yourself, you might want to be aware of some of the “gotchas” of implementing your own DAL, addressed by Davy Brion here, and Ayende Rahien here. Best of luck!

]]> By: seesharpgears http://www.sullivansoftdev.com/blog/2009/08/23/the-case-for-nhibernate/comment-page-1/#comment-156 seesharpgears Sun, 30 Aug 2009 03:07:12 +0000 http://www.sullivansoftdev.com/blog/?p=124#comment-156 Hello Brian, this was an exhaustively good article! You have started convincing me to abandon the usage of stored procedures, and start using some other type of data access! The ORM I have written myself in general uses stored procedures but binds the SQL table columns to C# class properties by itself, and it is capable of returning generic list of objects directly. I think I can extend my ORM so that it utilizes NHibernate but keep the mapping of the columns to properties automated, providing less development overhead ( yes, I am aware that automatization creates execution overhead! ). Do you think it would be more benefical to me write ? Here is my post about my ORM: <a href='http://seesharpgears.blogspot.com/2009/08/csharpgears-framework-object-relational.html' rel="nofollow">CsharpGears Framework: ORM</a> Hello Brian,
this was an exhaustively good article! You have started convincing me to abandon the usage of stored procedures, and start using some other type of data access! The ORM I have written myself in general uses stored procedures but binds the SQL table columns to C# class properties by itself, and it is capable of returning generic list of objects directly. I think I can extend my ORM so that it utilizes NHibernate but keep the mapping of the columns to properties automated, providing less development overhead ( yes, I am aware that automatization creates execution overhead! ). Do you think it would be more benefical to me write ?

Here is my post about my ORM: CsharpGears Framework: ORM

]]> By: Brian http://www.sullivansoftdev.com/blog/2009/08/23/the-case-for-nhibernate/comment-page-1/#comment-155 Brian Tue, 25 Aug 2009 14:24:03 +0000 http://www.sullivansoftdev.com/blog/?p=124#comment-155 Thanks, Kerry! :-) Thanks, Kerry! :-)

]]> By: Kerry Jenkins http://www.sullivansoftdev.com/blog/2009/08/23/the-case-for-nhibernate/comment-page-1/#comment-154 Kerry Jenkins Tue, 25 Aug 2009 14:20:56 +0000 http://www.sullivansoftdev.com/blog/?p=124#comment-154 Good writeup! Good writeup!

]]>