Scott Hanselman has produced a tour-de-force index of globalization links. [Via Ingo Rammer].
Brad Abrams explains in a post that the BCL team creates a directory for each namespace and a file for each type to easily find the source code of that type.
I've been surprised to find that some folks don't know that Visual Studio is all set up for this model. The general procedure is:
- Name the assembly as the base namespace of your assembly, such as System.Windows.Forms.dll. Alternatively, you can set the root namespace in the project settings.
- Create a folder for each namespace you will be using. To have nested namespaces, just nest your folders.
- When you create classes, use the Add New Class wizard from the context menu of the folder that represents the namespace where you want to define the class. This wizard will create the class within the appropriate namespace.
Go with the flow! Something Shawn Van Ness has acquiesced to. However, I'm with Chris Sells on the tabs/spaces issue.