On Dec 18, 11:07 pm, sbohlen <[email protected]> wrote: > Initializing mandatory values in the public ctor is a pretty common design > pattern. That's what the option of making the zero-arg ctor protected is > for -- its a middle-ground between the requirement NH has for a zero-arg > ctor and the desire to 'prevent' someone from new-ing up one of your > objects without providing the mandatory values. With the zero-arg ctor > protected, its still true that someone (reasonably clever) can obviously > derive from your class and access the zero-arg ctor that way, but otherwise > its 'shielded' from being 'casually' invoked by consumers of your objects.
Thanks Steve, that makes perfect sense, thanks very much. This is my first foray into ORM and your screencasts were simply wonderful. Thanks for taking the time to make them and provide them for download. Did you perchance publish the Autumn of Agile series as mentioned on the download page and here http://unhandled-exceptions.com/blog/index.php/2008/09/28/coming-soon-autumn-of-agile/? -- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
