Why do you create a DTO? Isn't it easier to create NHibernate mapping for the "smart" customer class?
On Mon, Oct 19, 2009 at 8:12 PM, YankeeImperialistDog <[email protected]> wrote: > > i'm really going overbord with DTO's in my quest for the "correct" > way. > > what do some of you consider correct for property naming? > > given a Customer and CustomerDTO (class) > > each with an id and a string for a Name property > > Customer.ID > Customer.Name > > what would the CustomerDTO properties be? > > Thanks > KES > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
