I would say you probably want all Value Objects to be serializable and
thus it would make sense to have standards such as "all solutions must
have a project specifically for value objects named
solution.ValueObjects" and "all value objects must be serializable"
and then you can have standard unit tests that can find all value
object projects within all solutions (assuming a well defined
hierarchy within source control) and enforce these standards.
HTH,
Sam
------------------------------------------------------------
We're hiring! B-Line Medical is seeking Mid/Sr. .NET
Developers for exciting positions in medical product
development in MD/DC. Work with a variety of technologies
in a relaxed team environment. See ads on Dice.com.
On 13 Feb 2007 08:26:46 -0800, "ph********@gmail.com"
<ph********@gmail.comwrote:
>We're trying to enforce serialization of all our widely used objects
at our company (our entire company's technology team is probably about
a hundred people) and are trying to come up with a good, automated way
of doing this.
We're considering asking people to explicitly put attributes on all
public objects designating if they are/aren't serializable.
Any thoughts on this being a good/bad idea and alternative solutions?