Do you name your assemblies consistently (<CompanyName>.<ComponentName>)?
10/20/2010 7:56 PM by
Assembly names should reflect the the functionality that it provides. For example,
contains all the classes that deal with inputs and outputs. As a general rule of thumb your assemblies should be named as follows:
<CompanyName>.<ComponentName> (e.g. SSW.Framework)
This allows a developer to know who developed the assembly and give the developer a general idea of what the assembly can be used for.
Do you feel this rule needs an update?