Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Port FxCop rule CA1044: PropertiesShouldNotBeWriteOnly #390

Open
ghost opened this issue Nov 21, 2015 · 1 comment
Open

Port FxCop rule CA1044: PropertiesShouldNotBeWriteOnly #390

ghost opened this issue Nov 21, 2015 · 1 comment

Comments

@ghost
Copy link

ghost commented Nov 21, 2015

Title: Properties should not be write only

Description:

Although it is acceptable and often necessary to have a read-only property, the design guidelines prohibit the use of write-only properties. This is because letting a user set a value, and then preventing the user from viewing that value, does not provide any security. Also, without read access, the state of shared objects cannot be viewed, which limits their usefulness.

Dependency: None

Notes:

@srivatsn
Copy link
Contributor

srivatsn commented Dec 3, 2015

Transitions bootcamp project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants