Comments on: Fluent NHibernate: Mapping private and protected properties http://jagregory.com/writings/fluent-nhibernate-mapping-private-and-protected-properties/ Monkeying with the code Fri, 26 Feb 2010 20:38:20 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Dew Drop - January 14, 2009 | Alvin Ashcraft's Morning Dew http://jagregory.com/writings/fluent-nhibernate-mapping-private-and-protected-properties/comment-page-1/#comment-15146 Dew Drop - January 14, 2009 | Alvin Ashcraft's Morning Dew Wed, 14 Jan 2009 19:36:13 +0000 http://blog.jagregory.com/?p=213#comment-15146 [...] Fluent NHibernate: Mapping Private and Protected Entities (James Gregory) [...] [...] Fluent NHibernate: Mapping Private and Protected Entities (James Gregory) [...]

]]> By: Reflective Perspective - Chris Alcock » The Morning Brew #264 http://jagregory.com/writings/fluent-nhibernate-mapping-private-and-protected-properties/comment-page-1/#comment-15132 Reflective Perspective - Chris Alcock » The Morning Brew #264 Wed, 14 Jan 2009 08:38:04 +0000 http://blog.jagregory.com/?p=213#comment-15132 [...] Fluent NHibernate: Mapping private and protected properties - James Gregory continues his exploration of Fluent NHIbernate looking at 3 techniques for mapping to private members with details of the Pros and Cons of each method. [...] [...] Fluent NHibernate: Mapping private and protected properties – James Gregory continues his exploration of Fluent NHIbernate looking at 3 techniques for mapping to private members with details of the Pros and Cons of each method. [...]

]]> By: Chris Marisic http://jagregory.com/writings/fluent-nhibernate-mapping-private-and-protected-properties/comment-page-1/#comment-15125 Chris Marisic Wed, 14 Jan 2009 06:50:46 +0000 http://blog.jagregory.com/?p=213#comment-15125 For as much as I think I know about C# in general every now and then I get made to feel stupid. Prior to this moment I didn't even know Class A { Class B { } } Was possible. Even with the discussions of the nested class approach for mapping private members I must have always glazed over and missed that the classes were truly inside each other not just next to each other. Out of all the solutions I personally feel Reveal is the best overall solution since it requires 0 modifications to your domain layer. The fact it does fall back onto string usage is a minor concern but for most developers I assume we all use Resharper to start with which should make the string renaming very easy for it to figure out. It still depresses me anytime I talk to a developer and they don't use Resharper or similar tool for development, I don't think I could ever go back to developing without it. I might as well use notepad to develop without Resharper. For as much as I think I know about C# in general every now and then I get made to feel stupid.

Prior to this moment I didn’t even know

Class A {
Class B { }
}

Was possible.

Even with the discussions of the nested class approach for mapping private members I must have always glazed over and missed that the classes were truly inside each other not just next to each other.

Out of all the solutions I personally feel Reveal is the best overall solution since it requires 0 modifications to your domain layer. The fact it does fall back onto string usage is a minor concern but for most developers I assume we all use Resharper to start with which should make the string renaming very easy for it to figure out.

It still depresses me anytime I talk to a developer and they don’t use Resharper or similar tool for development, I don’t think I could ever go back to developing without it. I might as well use notepad to develop without Resharper.

]]>