I was trying to use O2O Mapper and when I add to a collection on a Dto entity an existing entity the mapper create a new entity on the database. I think that this happens because the mapper.Compare function see that before the collection was empty, so it create a new entity on the DB. Is there a way to avoid this behavior?

asked Jul 18 '12 at 10:31

sluzardi's gravatar image


One Answer:

Hello sluzardi,

Support of O2O Mapper shipped with DataObjects.Net will be dropped soon, so it is recommended to use any other mapper implementation, e.g. AutoMapper or similar.

answered Jul 18 '12 at 11:09

Dmitri%20Maximov's gravatar image

Dmitri Maximov

Hi Dmitri,

"dropped soon", what does this means exactly? Do you bring new system for POCO? Because i have project based on DO.NET O2O...

(Jul 19 '12 at 02:42) Peter Ĺ ulek Peter%20%C5%A0ulek's gravatar image

Peter, don't panic. Although the current implementation of O2O mapper will be announced as deprecated, we will keep it in DataObjects.Net for some noticeable time.

(Jul 19 '12 at 04:26) Dmitri Maximov Dmitri%20Maximov's gravatar image

Will you come up with a replacement for the current O2O mapper that will also be able to replay changes into a session?

(Aug 14 '12 at 08:28) Sebastian Hauer Sebastian%20Hauer's gravatar image
Your answer
Please start posting your answer anonymously - your answer will be saved within the current session and published after you log in or create a new account. Please try to give a substantial answer, for discussions, please use comments and please do remember to vote (after you log in)!
toggle preview


Once you sign in you will be able to subscribe for any updates here



Asked: Jul 18 '12 at 10:31

Seen: 2,623 times

Last updated: Aug 14 '12 at 08:28

powered by OSQA