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.
It looks like the set accessor of an entity's primary key is labeled "private" even when the corresponding Property "Setter Visibility" is set to "Public".
The text was updated successfully, but these errors were encountered:
msawczyn
changed the title
Private setter for primary key
Identity properties ignore Setter Visibility setting
Nov 1, 2019
Thanks. SetterVisibility shouldn't be available for identity properties with generated properties; that change is now in place. Manual properties now obey the setter visibility.
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
Nov 10, 2019
Dear Michael, unfortunately, with version 1.3.0.10, my string manual identity columns keep getting generated with private setters, although the properties window shows public. I saw that if I set the setter to "Internal", then in the XML shows up a "setterVisibility" attribute for that entity property, however, when I set it to public, the "setterVisibility" attribute is missing.
EDIT: Forget it, my problem, I had not changed the ttinclude, I kept using my old one... Sorry for the false alarm.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
bugConfirmed bugreleasedIssue is resolved in a current release
It looks like the set accessor of an entity's primary key is labeled "private" even when the corresponding Property "Setter Visibility" is set to "Public".
The text was updated successfully, but these errors were encountered: