In his book, Eric Evans distinguishes between value classes and entity classes.  Value objects do not have an identity and continuity.Do Value classes contain behaviour? Is it acceptable for Value Types not to have behaviour? The reason I ask is because a rich domain model differs from an anemic one in the sense that classes contain state and behaviour.  I am trying to create a rich domain model, however I am finding myself creating value objects with no behaviour.  Therefore I wonder if my domain model is anemic (because the value types do not contain behaviour) and rich (because the entity types do contain behaviour). 
Do Value objects have behaviour?
c#;domain driven design
The distinction between value types and entities is largely independent of the amount of behavior that a class has.For entities, it is very unusual that they don't have behavior and that would be almost certainly an indication of an anemic domain model.For value types, you can have them with very rich behavior (like String) or with no behavior at all (typically DTO classes).If you want to keep away from anemic domain models, then you should avoid entities without behavior. That is, classes where multiple copies of an object shouldn't compare equal but that also don't contain behavior.