Fog Creek Software
Discussion Board




Welcome! and rules

Joel on Software

Assembly and Project naming conventions

I've noticed a standard of naming assemblies after their contained root namespace... i.e. System.Data.dll contains the System.Data namespace objects.

Do you think it is a good idea to also name your project after the root namespace?

The only downside I see is that it won't be easy to change the namespace in the future, if necessary.  The upside is that it's easy to know what goes with what.

Stress
Wednesday, August 06, 2003

It's pretty easy to rename projects, actually. :)

Brad Wilson (dotnetguy.techieswithcats.com)
Wednesday, August 06, 2003

I always use the namespace name for the assembly. Renaming projects is basically easy but IIRC the IDE doesn't actually rename the directories, so you have to manually do that (and manually correct he project files).

Chris Nahr
Thursday, August 07, 2003

Brad Adams has written some suggestions on this topic:

See Assembly/DLL Naming Guidelines
http://blogs.gotdotnet.com/BradA/permalink.aspx/b8ba029e-8208-410b-8e84-3850dc4762cf

Bernard Vander Beken
Thursday, August 07, 2003

Thanks for the replies.  I also found some msdn documentation that backs giving your assembly and project the same name as the root namespace.

See "Carefully Considering Naming Conventions" at the bottom of this page: http://tinyurl.com/jg5a

Stress
Friday, August 08, 2003

Stress,

The Brad A URL is likely to be the next version of the MSDN page, so you want to check that out as well. He's been posting a lot of changes the teams wants to make to the MSDN documentation to his blog to get public feedback.

Brad Wilson (dotnetguy.techieswithcats.com)
Friday, August 08, 2003

*  Recent Topics

*  Fog Creek Home