I know that this is somewhat subjective, but I wonder if there is a generally accepted standard for naming assemblies which contain some ‘core’ functions.
Let’s say you got a larger Projects, with Assemblies like
- Company.Product.WebControls.dll
- Company.Product.Net.dll
- Company.Product.UserPages.dll
and you have a Bunch of ‘Core’ classes, like the Global Error Handler, the global Logging functionality etc.
How would such an assembly generally named? Here are some things I had in mind:
- Company.Product.dll
- Company.Product.Core.dll
- Company.Product.Global.dll
- Company.Product.Administration.dll
Now, while ‘just pick one and go on’ will not cause Armageddon, I’d still like to know if there is an ‘accepted’ way to name those assemblies.
With .Net this is relatively easy to change, so I’d go with convenience.
Fewer, larger, assemblies compile quicker than many small ones, so I’d start with your ‘core’ stuff as a namespace inside Company.Product.dll, and split it out later if you need to.