[NotMapped] Attribute causes a cast error about detached-mapper HOT 2 CLOSED

Hi Nico,
Yup, there was a missing handler over there.. removed in 7.1.2.
I thought we agreed not to stop mapping for [NotMapped] but only for [MapIgnore].

A better workardound would be options.AnnotationHandlers.Remove(typeof(NotMappedAttribute));

Anyway, you already know how to create your own handlers, so, excellent..

from detached-mapper.

The problem was, it should still map the properties with NotMapped, which are not in the database.
Now when I remove NotMapped from the AnnotationHandlers Dictornary, it wants to load and track the Ef Core, but they are not in the database = error.
Suggested solution:
For the NotMapped attribute, map the values from the DTo to the entity, but don't try to load/track them from the database.

from detached-mapper.