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
We are using several db contexts. One of the contains enums we want to use in the other contexts. Because the Type-Property of entities is restricted to the select list we specified the type directly in the .efmodel file. Is there any reason not to remove the restriction of the type field in the designer?
Added the option Restrict property types to the designer's option page (Tools/Options/Entity Framework Visual Editor). Default is true, but setting it to false and reloading the designer will allow any property type to be typed in. Note that no validation is performed when this is done, so a bad type can be added. Best to use the fully qualified name of the type since there isn't a good way to get a namespace import into that file.
msawczyn
added
released
Issue is resolved in a current release
and removed
pending release
Issue is resolved in the current codebase, will be published with the next release
labels
Aug 25, 2022
From #40:
We are using several db contexts. One of the contains enums we want to use in the other contexts. Because the Type-Property of entities is restricted to the select list we specified the type directly in the .efmodel file. Is there any reason not to remove the restriction of the type field in the designer?
(submitted by @Jonathan4083)
The text was updated successfully, but these errors were encountered: