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
{{ message }}
This repository has been archived by the owner on Jan 16, 2024. It is now read-only.
I started trying this out today by importing a set of EF Core classes.
One thing that I had to do was to go through 50+ classes and mark the Id field as primary key.
EF Core automagically recognizes Id as being the primary key, so that doesn't need to be tagged by an attribute.
It would be practical if you could set an option to make EFDesigner do the same.
The text was updated successfully, but these errors were encountered:
To clarify, you're talking about drag/drop import of code onto the design surface, yes? The tool would, if it sees a property named Id, tag that property as an identity property when it imports the dropped class. Do I have that right?
I started trying this out today by importing a set of EF Core classes.
One thing that I had to do was to go through 50+ classes and mark the Id field as primary key.
EF Core automagically recognizes Id as being the primary key, so that doesn't need to be tagged by an attribute.
It would be practical if you could set an option to make EFDesigner do the same.
The text was updated successfully, but these errors were encountered: