POCO Best Practice
Posted
by Paul Johnson
on Stack Overflow
See other posts from Stack Overflow
or by Paul Johnson
Published on 2010-03-19T10:50:05Z
Indexed on
2010/03/19
10:51 UTC
Read the original article
Hit count: 677
All, I have a series of domain objects (project is NHibernate based). Currently as per 'good practice' they define only the business objects, comprising properties and methods specific to each objects function within the domain. However one of the objects has a requirement to send an SMTP message. I have a simple SMTP client class defined in a separate 'Utilities' assembly. In order to use this mail client from within the POCO, I would need to hold a reference to the utilities assembly in the domain. My query is this... Is it a departure from best practice to hold such a reference in a POCO, for the purpose of gaining necessary business functionality.
Kind Regards
Paul J.
© Stack Overflow or respective owner