Do you name your assemblies consistently (<CompanyName>.<ComponentName>)?
Last updated by Brady Stroud [SSW] about 2 months ago.See history This rule has been archived
Archived Reason: already covered by rule https://www.ssw.com.au/rules/do-you-have-a-consistent-net-solution-structure
Assembly names should reflect the the functionality that it provides. For example,
System.IOcontains 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.
Love it
0
Agree
0
Disagree
0
No way
0
