access-modifiers

I have three classes. all are part of the same namespace. here are the basics of the three classes. //FBlock.cs namespace StubGenerator.PropGenerator { class FBlock : IDesignRegionInserts, IFormRegionInserts, IAPIRegionInserts, IConfigurationInserts, ISoapProxyClientInserts, ISoapProxyServiceInserts { private List<Property> pProperties; private List<Method> pMethods; public FBlock(string aFBlockName) { pProperties = new List<Property>(); pMethods = new List<Method>(); } public Property AddProperty(string aName) { Property loProp = new Property(this, aName, pProperties.Count); pProperties.Add

If I will create a new object like the following, which access modifier will it have by default? Object objectA = new Object(); Any member will always have the most restrictive one available - so in this case the accessibility of objectA is private . (Assuming it's an instance variable. It makes no sense as a local variable, as they don't have any access rules as such.) So this: class Foo { Object objectA = new Object(); } is equivalent to this: internal class Foo { private Object objectA = new Object(); } The "default to most private" means that for types, the accessibility depends on the

I have a common assembly/project that has an abstract base class, then several derived classes that I want to make public to other assemblies. I don't want the abstract base class to show up in these other assemblies in Intellisense, so I thought I'd make it internal , but I get this error: Inconsistent accessibility: base class 'Settings' is less accessible than class 'IrcSettings' .... I don't really get this. I am forced to make the abstract Settings class public , and thus visible outside this assembly. How can I make this class internal instead? As I understand, you want your abstract

As far as I know, private is the default everywhere in C# (meaning that if I don't write public , protected , internal , etc. it will be private by default). (Please correct me if I am wrong.) So, what's the reason to write that keyword, or why does it even exist for members? For example, when an event handler is auto-generated it looks like this: private void RatTrap_MouseEnter(object sender, CheeseEventArgs e) { } But why does it even write private if that's implied and default? Just so that novice developers (who don't know it's the C# default) know that it's private? Or is there a

While dabbling with Typescript I realised my classes within modules (used as namespaces) were not available to other classes unless I wrote the export keyword before them, such as: module some.namespace.here { export class SomeClass{..} } So now I can use the above code like this: var someVar = new some.namespace.here.SomeClass(); However I was just wondering why this keyword is used opposed to just using the public keyword which is used at method level to signify that a method or property should be externally accessible. So why not just use this same mechanism to make classes and interfaces