Namespace naming conventions?

From the Namespace Naming Guidelines : The general rule for naming namespaces is to use the company name followed by the technology name and optionally the feature and design as follows. Copy Code CompanyName.TechnologyName.Feature. Design Generally it's a really bad practice to start including things into the default namespace of a framework or library.

This can cause confusion in terms of whether a new namespace is part of the existing library that is part of a framework that is distributed to everyone, or is part of a custom framework that was added by someone else Also, the naming convention tries to avoid namespace collisions by having unique identifiers such as CompanyName It also reduces any confusion and issues in terms of the source of the new library This is not only a Microsoft thing, but in the Java as well. Namespaces in Java, called "packages" has the following convention : The prefix of a unique package name is always written in all-lowercase ASCII letters and should be one of the top-level domain names, currently com, edu, gov, mil, net, org, or one of the English two-letter codes identifying countries as specified in ISO Standard 3166, 1981 Subsequent components of the package name vary according to an organization's own internal naming conventions. Such conventions might specify that certain directory name components be division, department, project, machine, or login names So, if I had a super awesome piece of software, it may be in the net.coobird.

Superawesomesoftware package And using package names that contain the default java javax com. Sun packages are a big no-no.

From the Namespace Naming Guidelines: The general rule for naming namespaces is to use the company name followed by the technology name and optionally the feature and design as follows. Copy Code CompanyName.TechnologyName.Feature. Design Generally it's a really bad practice to start including things into the default namespace of a framework or library.

This can cause confusion in terms of whether a new namespace is part of the existing library that is part of a framework that is distributed to everyone, or is part of a custom framework that was added by someone else. Also, the naming convention tries to avoid namespace collisions by having unique identifiers such as CompanyName. It also reduces any confusion and issues in terms of the source of the new library.

This is not only a Microsoft thing, but in the Java as well. Namespaces in Java, called "packages" has the following convention: The prefix of a unique package name is always written in all-lowercase ASCII letters and should be one of the top-level domain names, currently com, edu, gov, mil, net, org, or one of the English two-letter codes identifying countries as specified in ISO Standard 3166, 1981. Subsequent components of the package name vary according to an organization's own internal naming conventions.

Such conventions might specify that certain directory name components be division, department, project, machine, or login names. So, if I had a super awesome piece of software, it may be in the net.coobird. Superawesomesoftware package.

And using package names that contain the default java. , javax. , com.sun.

Packages are a big no-no.

Sir Psycho: Coobird is right but you also need to keep an open mind set you don't want a namespace that ends up being too deep. I start getting worried after I type 3 '. ' in a namespace name.

– Perpetualcoder May 28 '09 at 2:47 @Sir Psycho: The namespace guidelines also says that an well-established brand is another option instead of a company name -- these are guidelines to avoid namespace collisions. So, perhaps some title (like your username? ) that is unique from others may be a good substitute for CompanyName :) – coobird May 28 '09 at 3:21 @Perpetualcoder If you're worried about too deep namespaces, use alias... – LILkillaBEE Sep 13 at 7:25 @LILkilaaBEE: Alias is good when you are consuming these namespaces.

Doesn't make the namespace concise in itself. – Perpetualcoder Sep 13 at 14:57.

Also have a look at this MSDN article for guidelines for naming Namespaces Names of Namespaces: msdn.microsoft.com/en-us/library/ms22902....

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.