Comments on: How-To: Using the N* Stack, part 3 http://jasondentler.com/blog/2009/08/how-to-using-the-n-stack-part-3/ I'm just here for the code Mon, 06 Sep 2010 12:21:16 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Part 5: Fixing the Broken Stuff - NHibernate blog - NHibernate Forge http://jasondentler.com/blog/2009/08/how-to-using-the-n-stack-part-3/comment-page-1/#comment-120 Part 5: Fixing the Broken Stuff - NHibernate blog - NHibernate Forge Sat, 22 Aug 2009 14:14:07 +0000 http://jasondentler.com/blog/2009/08/how-to-using-the-n-stack-part-3/#comment-120 [...] Part 3 – Persistence mapping [...] [...] Part 3 – Persistence mapping [...]

]]> By: Part 5: Fixing the Broken Stuff « BASICly everything http://jasondentler.com/blog/2009/08/how-to-using-the-n-stack-part-3/comment-page-1/#comment-118 Part 5: Fixing the Broken Stuff « BASICly everything Sat, 22 Aug 2009 13:47:01 +0000 http://jasondentler.com/blog/2009/08/how-to-using-the-n-stack-part-3/#comment-118 [...] Part 3 – Persistence mapping [...] [...] Part 3 – Persistence mapping [...]

]]> By: Norbert Beckers http://jasondentler.com/blog/2009/08/how-to-using-the-n-stack-part-3/comment-page-1/#comment-101 Norbert Beckers Thu, 20 Aug 2009 06:59:14 +0000 http://jasondentler.com/blog/2009/08/how-to-using-the-n-stack-part-3/#comment-101 No Thanks. Changes go fast I reckon...;-}~ No Thanks. Changes go fast I reckon…;-}~

]]> By: Jason http://jasondentler.com/blog/2009/08/how-to-using-the-n-stack-part-3/comment-page-1/#comment-99 Jason Wed, 19 Aug 2009 18:47:41 +0000 http://jasondentler.com/blog/2009/08/how-to-using-the-n-stack-part-3/#comment-99 @Rob - Functionally, they are identical. Either will work. Personally, I prefer the shorter AddFromAssemblyOf method. The method name indicates that you are dealing with the assembly containing the type, not the type specifically. @Rob – Functionally, they are identical. Either will work.

Personally, I prefer the shorter AddFromAssemblyOf method. The method name indicates that you are dealing with the assembly containing the type, not the type specifically.

]]> By: Rob Bihun http://jasondentler.com/blog/2009/08/how-to-using-the-n-stack-part-3/comment-page-1/#comment-98 Rob Bihun Wed, 19 Aug 2009 15:12:54 +0000 http://jasondentler.com/blog/2009/08/how-to-using-the-n-stack-part-3/#comment-98 In your configuration.cs (line # 26 in this post) you have: .Mappings(x => x.FluentMappings.AddFromAssemblyOf() .ExportTo(m_SchemaPath)) Is this better than: .Mappings(x => x.FluentMappings.AddFromAssembly(Assembly.GetAssembly(this.GetType())).ExportTo(m_SchemaPath)) Forgive me if this is an ignorant question, I am just now starting to play with NHibernate. To me your post (before looking closely) looks like you are doing something specifically with the CourseMapping class and not all the classes that inherit ClassMap... which in this case are all contained in NStackExample.Data along with the configuration class. In your configuration.cs (line # 26 in this post) you have:

.Mappings(x => x.FluentMappings.AddFromAssemblyOf()
.ExportTo(m_SchemaPath))

Is this better than:

.Mappings(x =>
x.FluentMappings.AddFromAssembly(Assembly.GetAssembly(this.GetType())).ExportTo(m_SchemaPath))

Forgive me if this is an ignorant question, I am just now starting to play with NHibernate. To me your post (before looking closely) looks like you are doing something specifically with the CourseMapping class and not all the classes that inherit ClassMap… which in this case are all contained in NStackExample.Data along with the configuration class.

]]> By: Jason http://jasondentler.com/blog/2009/08/how-to-using-the-n-stack-part-3/comment-page-1/#comment-97 Jason Wed, 19 Aug 2009 15:06:06 +0000 http://jasondentler.com/blog/2009/08/how-to-using-the-n-stack-part-3/#comment-97 @Norbert - v1 RC was released less than 48 hours ago. I'll include those updates in my next post. Thanks. @Norbert – v1 RC was released less than 48 hours ago. I’ll include those updates in my next post. Thanks.

]]> By: Norbert Beckers http://jasondentler.com/blog/2009/08/how-to-using-the-n-stack-part-3/comment-page-1/#comment-95 Norbert Beckers Wed, 19 Aug 2009 07:49:47 +0000 http://jasondentler.com/blog/2009/08/how-to-using-the-n-stack-part-3/#comment-95 Update: "WithForeignKeyConstraintName(String)" now is "ForeignKeyConstraintName(String)" Update: “WithForeignKeyConstraintName(String)” now is “ForeignKeyConstraintName(String)”

]]> By: Norbert Beckers http://jasondentler.com/blog/2009/08/how-to-using-the-n-stack-part-3/comment-page-1/#comment-94 Norbert Beckers Wed, 19 Aug 2009 07:36:36 +0000 http://jasondentler.com/blog/2009/08/how-to-using-the-n-stack-part-3/#comment-94 This series isn't up to date. I'm using 1.0RC, the latest release version of FluentNHibernate. The "WithLengthOf(Int32)" method is replaced by "Length(Int32)" This series isn’t up to date. I’m using 1.0RC, the latest release version of FluentNHibernate. The “WithLengthOf(Int32)” method is replaced by “Length(Int32)”

]]> By: José F. Romaniello http://jasondentler.com/blog/2009/08/how-to-using-the-n-stack-part-3/comment-page-1/#comment-93 José F. Romaniello Tue, 18 Aug 2009 20:13:24 +0000 http://jasondentler.com/blog/2009/08/how-to-using-the-n-stack-part-3/#comment-93 I agree with you. I agree with you.

]]> By: Jason http://jasondentler.com/blog/2009/08/how-to-using-the-n-stack-part-3/comment-page-1/#comment-86 Jason Tue, 18 Aug 2009 14:05:57 +0000 http://jasondentler.com/blog/2009/08/how-to-using-the-n-stack-part-3/#comment-86 Yes. I did compare an FNH generated xml mapping to FNH code. You've stripped out some property types and assembly-qualified type names, and it is cleaner. If I had one handy, I probably would have used a hand-written mapping from a greenfield project. Looking back, it does come across as a dishonest comparison. I do agree that hand-written XML mappings are usually more readable than those generated by FNH, but as I understand it, that's not the goal of the FNH project. I really just have two points: #1 - Even in their simplest form, XML mappings are still more difficult to read, and more importantly, more difficult to maintain than an FNH mapping written in C#. Of course, to a degree, readability and even maintainability are subjective. I don't agree with the "enterprise Java" point of view that XML is the perfect solution for everything. I think you pay a VERY heavy "magic strings" tax with XML in general, and especially when a lot of XML has to stay in sync with a lot of code, as in the case of mappings. In one of the most critical locations in the applications, that's just unacceptable - again, just my opinion. XML has it's place. It's great for standard communications protocols and configuration settings that are likely to change as the hardware and network change. In the case of mappings, it's being used more as a replacement for code. It feels wrong to me. #2 - XML mappings will slow the adoption of NHibernate. FNH is a success partly because it abuses the hell out of Intellisense to flatten out the NH learning curve. I'm not bashing NHibernate. It's an amazing ORM, and the XML mappings are part of its history. They also make a great integration point for codegen tools. I think as NHibernate is adopted outside of the ALT.NET community, you'll see a lot less hand-written mappings and a lot more codegen, DB reverse-engineer, and FNH mappings. In case it wasn't obvious already, I'm pretty new to NHibernate. I'm still making rookie mistakes. The learning curve for NHibernate for a newbie in a "hurry up and get it done" drag-n-drop programming shop is pretty steep. Add in these weird little XML mappings that refuse to stay in sync with the model and the newbie might just choose EF and its GUI designers over NHibernate. Now that FNH is officially v1 RC, NH could serve itself well to push FNH to beginners as an easy one-size-fits-most mapping solution while still supporting the XML mappings for advanced fine-tuning. But that's for Fabio to decide, not me. Yes. I did compare an FNH generated xml mapping to FNH code. You’ve stripped out some property types and assembly-qualified type names, and it is cleaner. If I had one handy, I probably would have used a hand-written mapping from a greenfield project. Looking back, it does come across as a dishonest comparison.

I do agree that hand-written XML mappings are usually more readable than those generated by FNH, but as I understand it, that’s not the goal of the FNH project.

I really just have two points:
#1 – Even in their simplest form, XML mappings are still more difficult to read, and more importantly, more difficult to maintain than an FNH mapping written in C#. Of course, to a degree, readability and even maintainability are subjective.

I don’t agree with the “enterprise Java” point of view that XML is the perfect solution for everything. I think you pay a VERY heavy “magic strings” tax with XML in general, and especially when a lot of XML has to stay in sync with a lot of code, as in the case of mappings. In one of the most critical locations in the applications, that’s just unacceptable – again, just my opinion.

XML has it’s place. It’s great for standard communications protocols and configuration settings that are likely to change as the hardware and network change. In the case of mappings, it’s being used more as a replacement for code. It feels wrong to me.

#2 – XML mappings will slow the adoption of NHibernate. FNH is a success partly because it abuses the hell out of Intellisense to flatten out the NH learning curve.

I’m not bashing NHibernate. It’s an amazing ORM, and the XML mappings are part of its history. They also make a great integration point for codegen tools. I think as NHibernate is adopted outside of the ALT.NET community, you’ll see a lot less hand-written mappings and a lot more codegen, DB reverse-engineer, and FNH mappings.

In case it wasn’t obvious already, I’m pretty new to NHibernate. I’m still making rookie mistakes. The learning curve for NHibernate for a newbie in a “hurry up and get it done” drag-n-drop programming shop is pretty steep. Add in these weird little XML mappings that refuse to stay in sync with the model and the newbie might just choose EF and its GUI designers over NHibernate.

Now that FNH is officially v1 RC, NH could serve itself well to push FNH to beginners as an easy one-size-fits-most mapping solution while still supporting the XML mappings for advanced fine-tuning. But that’s for Fabio to decide, not me.

]]>