The easy way to remember it (IMO) is that C# assumes you want the most
restricted access available for anything. That's great, because it
means you can cheerfully go with the defaults and get a visual reminder
(in the form of an accessibility keyword) when you *don't* want the
most private access. Making things "more private" is much less likely
to be a mistake than making things "less private", as it will be picked
up at compile time. (The exception to this rule is when reflection is
used, of course.)
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.