-
Notifications
You must be signed in to change notification settings - Fork 507
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
SA1202 wrongly treats explicit interface implementations as private #1179
Comments
Ugh. 🐛 I'm glad you are so persistent with checking these. 😄 Marking up for grabs although I expect @Noryoko will jump on it. |
You would be correct in that assumption. |
2 tasks
@marcospgp, this issue was marked as fixed in 2015, so it was definitely resolved. Please create a new issue with a small but complete example that it misbehaves on if you are seeing unwanted behavior. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Legacy StyleCop correctly treats members that explicitly implement an interface member as public. The new analyzers, however, treat these as private.
Interestingly, explicit implementations are treated as public by legacy StyleCop even when they implement an internal interface. (I used an internal interface in my example; the results are the same if you make it public.)
Sorry I missed this subtlety before.
The text was updated successfully, but these errors were encountered: