c# - Why does FxCop treat protected as public? -


Why does FxCop treat protected members like they are throwing DoNotDeclareVisibleInstanceFields error? I am pretty sure that the protected member is a valid code design.

I'm not sure what it meant to you, but the general protected members included a class interface Are the part.

You do not want public member variables because they make your implementation inflexible. Protected member variables do only because the classes you receive will depend on them, thus making your implementation inflexible.

Asph


Comments

Popular posts from this blog

asp.net - Javascript/DOM Why is does my form not support submit()? -

sockets - Delphi: TTcpServer, connection reset when reading -

javascript - Classic ASP "ExecuteGlobal" statement acting differently on two servers -