Skip to content
This repository has been archived by the owner on Jan 16, 2024. It is now read-only.

Identity properties ignore Setter Visibility setting #118

Closed
alprinias opened this issue Oct 30, 2019 · 2 comments
Closed

Identity properties ignore Setter Visibility setting #118

alprinias opened this issue Oct 30, 2019 · 2 comments
Labels
bug Confirmed bug released Issue is resolved in a current release
Projects
Milestone

Comments

@alprinias
Copy link

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".

@msawczyn msawczyn changed the title Private setter for primary key Identity properties ignore Setter Visibility setting Nov 1, 2019
@msawczyn
Copy link
Owner

msawczyn commented Nov 9, 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 msawczyn added bug Confirmed bug pending release Issue is resolved in the current codebase, will be published with the next release labels Nov 9, 2019
@msawczyn msawczyn added this to Enhancement Triage in EFDesigner via automation Nov 9, 2019
@msawczyn msawczyn moved this from Enhancement Triage to Done in EFDesigner Nov 9, 2019
@msawczyn msawczyn added this to the 1.3.0.8 milestone Nov 9, 2019
@msawczyn 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
@alprinias
Copy link
Author

alprinias commented Nov 13, 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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Confirmed bug released Issue is resolved in a current release
Projects
EFDesigner
  
Done
Development

No branches or pull requests

2 participants