This project is read-only.

Assembly and Namespace Naming

Topics: Developer Forum
Jan 30, 2007 at 2:25 PM
again just a few thoughts to get people thinking. THe way I normally do things is have everything inside a root namespace i.e. Serenity

I then name the assemblies as thier root namespace i.e. Serenity.Server, Serenity.Data

For executables I always give them the applicaiton name, but sometimes i name the application with a single name i.e. SerenityConsole or as the namespace i.e. Serenity.Console.

Not sure what you currently use or what your thoughts are but it'd be good to get a standard set down :)
Jan 30, 2007 at 7:20 PM
Right now, pretty much everything is in just one assembly (Serenity) to allow more flexibility, for example to reduce the chance of a circular reference.

I've named the other "core" projects with the "dot-naming" scheme, so Serenity.Server is the console server application, Serenity.Service is the system service, and Serenity.Service.Control is the Control UI application.
Jan 31, 2007 at 3:53 PM
Cool :)