Remove StyleCop suppressions and resolve style issues #194
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adhering to default StyleCop recommendations i.e., using
this.
in front of the instance variables. This way is more consistent since otherwise we use variables with names like_varName
for private instance fields, and names likeVarName
for public and private static fields and public instance properties. When referencing one of these variables in rest of the class, havingthis.
prefixed makes it clear to the reader whether instance or static or local variable is being accessed. In that case, the underscore prefix becomes irrelevant. Similar justification can be found in StyleCop documentation here and here.