Comments on: Managing NHibernate Maps http://laribee.com/managing-nhibernate-maps There are eight million stories in Cloud City; this is just one. Tue, 09 Mar 2010 19:48:21 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Ben Scheirman http://laribee.com/managing-nhibernate-maps/comment-page-1#comment-114 Ben Scheirman Tue, 15 Dec 2009 01:45:11 +0000 http://laribee.com/blog/2007/01/15/managing-nhibernate-maps/#comment-114 I have followed the mapping-per-concrete-class strategy and I like it a lot. I get used to seeing 2 of every class (Item.cs, Item.hbm.xml for example).<br><br>It's a matter of personal preference, but I find that method the easiest to manage. I have followed the mapping-per-concrete-class strategy and I like it a lot. I get used to seeing 2 of every class (Item.cs, Item.hbm.xml for example).

It's a matter of personal preference, but I find that method the easiest to manage.

]]> By: Eduard Liebenberger http://laribee.com/managing-nhibernate-maps/comment-page-1#comment-113 Eduard Liebenberger Wed, 09 May 2007 23:52:01 +0000 http://laribee.com/blog/2007/01/15/managing-nhibernate-maps/#comment-113 It means that you have to set the "skipOrder" parameter to "false" when you use calls like "Configuration.AddAssembly" etc. NHibernate documentation recommends to set this parameter to "true" to increase performance (and I believe this is the default setting). And in case you manually add the mapping files you already mentioned that it will be the developer's responsibility to keep a proper order. However if the mapping files (and the inheritance hierarchies) are split across multiple assemblies the configuration is still not totally robust (Release 1.2 GA). It means that you have to set the “skipOrder” parameter to “false” when you use calls like “Configuration.AddAssembly” etc. NHibernate documentation recommends to set this parameter to “true” to increase performance (and I believe this is the default setting).
And in case you manually add the mapping files you already mentioned that it will be the developer’s responsibility to keep a proper order.

However if the mapping files (and the inheritance hierarchies) are split across multiple assemblies the configuration is still not totally robust (Release 1.2 GA).

]]> By: Ben Scheirman http://laribee.com/managing-nhibernate-maps/comment-page-1#comment-112 Ben Scheirman Sat, 27 Jan 2007 18:22:24 +0000 http://laribee.com/blog/2007/01/15/managing-nhibernate-maps/#comment-112 I have followed the mapping-per-concrete-class strategy and I like it a lot. I get used to seeing 2 of every class (Item.cs, Item.hbm.xml for example). It's a matter of personal preference, but I find that method the easiest to manage. I have followed the mapping-per-concrete-class strategy and I like it a lot. I get used to seeing 2 of every class (Item.cs, Item.hbm.xml for example).

It’s a matter of personal preference, but I find that method the easiest to manage.

]]> By: Evan http://laribee.com/managing-nhibernate-maps/comment-page-1#comment-111 Evan Tue, 16 Jan 2007 01:42:34 +0000 http://laribee.com/blog/2007/01/15/managing-nhibernate-maps/#comment-111 This is some really good practical advice! Thanks for sharing. :-) This is some really good practical advice! Thanks for sharing. :-)

]]> By: DotNetKicks.com http://laribee.com/managing-nhibernate-maps/comment-page-1#comment-110 DotNetKicks.com Mon, 15 Jan 2007 17:43:39 +0000 http://laribee.com/blog/2007/01/15/managing-nhibernate-maps/#comment-110 <strong>Managing NHibernate Maps...</strong> You've been kicked (a good thing) - Trackback from DotNetKicks.com... Managing NHibernate Maps…

You’ve been kicked (a good thing) – Trackback from DotNetKicks.com…

]]>