access-modifiers

I just realized that the C# property construct can also be used with a private access modifier: private string Password { get; set; } Although this is technically interesting, I can't imagine when I would use it since a private field involves even less ceremony : private string _password; and I can't imagine when I would ever need to be able to internally get but not set or set but not get a private field: private string Password { get; } or private string Password { set; } but perhaps there is a use case with nested / inherited classes or perhaps where a get/set might contain logic instead of

This code: abstract class C { protected abstract void F(D d); } class D : C { protected override void F(D d) { } void G(C c) { c.F(this); } } Generates this error: Cannot access protected member 'C.F(D)' via a qualifier of type 'C'; the qualifier must be of type 'D' (or derived from it) What in the world were they thinking? (Would altering that rule break something?) And is there a way around that aside from making F public? Edit: I now get the reason for why this is (Thanks Greg ) but I'm still a bit perplexed as to the rational; given: class E : C { protected override void F(D d) { } } Why

Here is my shortened abstract class: abstract class Report { protected internal abstract string[] Headers { get; protected set; } } Here is a derived class: class OnlineStatusReport : Report { static string[] headers = new string[] { "Time", "Message" } protected internal override string[] Headers { get { return headers; } protected set { headers = value; } } internal OnlineStatusReport() { Headers = headers; } } The idea is, I want to be able to call Report.Headers from anywhere in the assembly, but only allow it to be set by derived classes. I tried making Headers just internal, but

What is the equivalent of Java's final in C#? Noldorin The final keyword has several usages in Java. It corresponds to both the sealed and readonly keywords in C#, depending on the context in which it is used. Classes To prevent subclassing (inheritance from the defined class): Java public final class MyFinalClass {...} C# public sealed class MyFinalClass {...} Methods Prevent overriding of a virtual method. Java public class MyClass { public final void myFinalMethod() {...} } C# public class MyClass : MyBaseClass { public sealed override void MyFinalMethod() {...} } As Joachim Sauer points

Could you please explain what the practical usage is for the internal keyword in C#? I know that the internal modifier limits access to the current assembly, but when and in which circumstance should I use it? Ash Utility or helper classes/methods that you would like to access from many other classes within the same assembly, but that you want to ensure code in other assemblies can't access. From MSDN (via archive.org): A common use of internal access is in component-based development because it enables a group of components to cooperate in a private manner without being exposed to the rest of

In VB6/VBA, you can declare module-level variables outside of a specific Sub or Function method. I've used Private and Public before inside modules and understand them like so: Public - visible to all code inside the module and all code outside the module, essentially making it global. Private - visible only to code inside the module. I've noticed that you can use Dim and Global as modifiers for modular variables. Are Dim and Global different from Private and Public , respectively, when used as access modifiers on modular fields? If so, how are they different? Joe Jordan Dim and Private work