Namespace & Assembly Naming

Coordinator
Jun 28, 2007 at 4:47 AM
Edited Jun 28, 2007 at 4:48 AM
As we're going to merge two projects and create a single one which covers several different pieces of code, I think it's better to create a single MSBuild file for the project to automate the process of merging all projects into one assembly like what Thommi has done for our CSModules project.

We also need a spec about namespaces. Here is my suggestion:

  • Root namespace: CommunityServerStuff
  • Controls: CommunityServerStuff.Controls
  • CSModules: CommunityServerStuff.CSModules
  • CSJobs: CommunityServerStuff.CSJobs
  • HttpModules: CommunityServerStuff.HttpModules
  • Handlers: CommunityServerStuff.Handlers

Ideas?
Developer
Jun 29, 2007 at 7:49 PM
Yeah, CSModules is a mess as regards the multiple projects. Having a single project makes both debugging and deployment much easier.

The namespaces make sense. I´m fine with them.
Developer
Jun 30, 2007 at 3:50 AM
Looks good. The only suggestion I have for namespaces is to make it HttpHandlers vs. Handlers to be consistent.

If I may make a suggestion for the physical structure, organize the controls folder similar to how CS is organized. For example, put all the Forms controls into the Forms folder. It'll help keep it organized and make it quicker to find the type of control you're looking for.