How do you name your spaces?

[Nagy Vilmos]

I follow the Java standard for package names, so everything is under com.vilmos. Actually that's a lie, it's mostly `com.lexa`, but that's because there is a master project called Lexa.

veni bibi saltavi

[Ian Shlasko]

Bleh, I hate that convention... Why, when I'm searching through my endless list of dependencies (Don't get me started...), should I have to remember whether it's a com, net, or org? .NET just does it better (Like so many things)... Anything in the basic framework is System.*, anything Windows-specific is Microsoft.*, and anything else is CompanyName.* or LibraryName.*

Proud to have finally moved to the A-Ark. Which one are you in?
Author of the Guardians Saga (Sci-Fi/Fantasy novels)

[Slacker007]

I use the alphabet. a.b.c etc... j/k CompanyName.SoftwareProjectName.VisualStudioProjectName (ACME.RoadRunner.DAL) or something like that. or SoftwareProjectName.VisualStudioProjectName (RoadRunner.DAL) or something like that.

[PIEBALDconsult]

PIEBALD
PIEBALD.Lib
PIEBALD.Data
PIEBALD.Type

etc.

[Jorgen Andersson]

According to standard[^].

Wrong is evil and must be defeated. - Jeff Ello

[Kevin Marois]

Since a solution can contain projects directly related to an app, as well as commonly shared projects, I use the following. Note that not all are needed: ** For the app itself Company.Project.Core Company.Project.DAL Company.Project.BL Company.Project.Entities Company.Project.Shared Company.Project.Tools Company.Project.UI.WPF.Controls Company.Project.UI.WPF.Desktop Company.Project.UI.WPF.Phone Company.Project.UI.WPF.Tablet Company.Project.UI.Web.MVC ** Projects shared by many apps Company.WPF.Controls Company.WPF.Entities Company.WPF.Themes Company.WPF.Utilites

If it's not broken, fix it until it is

[CHill60]

Me too. If I get the chance. As a contractor I either have to be "whiter than white" (which is why I follow the M$ way whenever possible) or have to adhere to local convention, regardless of how silly it might be :sigh:

[Gary Wheeler]

Since the source code for our projects is proprietary, we omit the company identification from the namespace name. For .NET, our namespaces are _Assembly_{.Package} where _Assembly_ is the assembly name and the {.Package} suffix is only used where an assembly contains more than one significant body of code. For C++ we usually just use the global namespace. I did have one C++ project where a combination of namespace's and a templated base class really improved the readability of a pile of related classes.

Software Zen: delete this;

[Lost User]

Last time I needed a namespace, I happened to play a game. My new commander had just arrived at my base and yelled "Forces of chaos, bow to me!" So my new namespace became FoC, which is very accurate for most software projects.

The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a fucking golf cart.
"I don't know, extraterrestrial?" "You mean like from space?" "No, from Canada." If software development were a circus, we would all be the clowns.

[Nueman]

Slacker007 wrote:

ACME.RoadRunner

beep beep

What we got here is a failure to communicate

[Slacker007]

:-D :thumbsup:

[PIEBALDconsult]

"CONSIDER using plural namespace names where appropriate." Never pluralize.

[Jorgen Andersson]

And your reasoning is?

Wrong is evil and must be defeated. - Jeff Ello

[Sander Rossel]

Sander.CatOwner, I like it! Gives a personal touch to my software :laugh:

Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.

Simplicity is prerequisite for reliability. — Edsger W. Dijkstra

Regards, Sander

[Sander Rossel]

Well, Nika DOES love to sleep behind the computer, just like her owner :D

Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.

Simplicity is prerequisite for reliability. — Edsger W. Dijkstra

Regards, Sander

[Sander Rossel]

Nagy Vilmos wrote:

there is a master project called Lexa

The #1 Dutch dating site? :omg:

Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.

Simplicity is prerequisite for reliability. — Edsger W. Dijkstra

Regards, Sander

[Sander Rossel]

Slacker007 wrote:

ACME.RoadRunner

Well, at least that ACME stuff crashed about as often as Visual Studio :laugh: :thumbsup:

Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.

Simplicity is prerequisite for reliability. — Edsger W. Dijkstra

Regards, Sander

[Sander Rossel]

That's a rule for database tables :)

Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.

Simplicity is prerequisite for reliability. — Edsger W. Dijkstra

Regards, Sander

[Sander Rossel]

MSDN wrote:

X DO NOT use the same name for a namespace and a type in that namespace.

HATE it when that happens :sigh:

Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.

Simplicity is prerequisite for reliability. — Edsger W. Dijkstra

Regards, Sander

[PIEBALDconsult]

And still a bad idea.