You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In EF6 I used Complex Types for value objects. I thought that owned entities is the way to do ValueObjects in EF Core.
Owned entities is the approach recommended in: ".NET microservices - Architecture e-book".
Why owned entities are not a good fit?
What is the recommended way to implement Value Objects?
Thank you all for a great product.
The text was updated successfully, but these errors were encountered:
Owned types are not a good fit because they have keys, even though the key might be hidden. This results in non-obvious behaviors when value objects are used as if they did not have keys. See this comment and the linked issues for some more discussion.
Hi,
In @JeremyLikness blog post: "The Plan for Entity Framework Core 6.0" there is a section about Domain-Driven Design Value Objects:
In EF6 I used Complex Types for value objects. I thought that owned entities is the way to do ValueObjects in EF Core.
Owned entities is the approach recommended in: ".NET microservices - Architecture e-book".
Why owned entities are not a good fit?
What is the recommended way to implement Value Objects?
Thank you all for a great product.
The text was updated successfully, but these errors were encountered: