As a beginner/intermediate developer one problem I run into as my projects get bigger and more abstracted away as i use more OOP principles I have a problem with naming things. Like when i have multiple projects or class libraries I don’t know what to name them. I see things from xxx.Core to xxx.Main or have even seen xxx.BLL and xxx.DAL. While looking through others i have seen xxx.Services and xxx.Data for their library and namespaces.
Then once that is solved is what do i cal DTO’s? In that realm i have seen xxx.DTO, xxx.Entities, xxx.Props.
What are some good guidelines to naming libraries, methods, interfaces, etc… while coding so that more and more people will understand things when they come to pick up the project after me.
Abbreviations are in general bad.
Data Access Layer
YourCompany.Data.dll
Entity Layer
YourCompany.Data.Entities.dll
Business Layer
YourCompany.BusinessLogic.Name.dll (example: YourCompany.Accounting.Services.dll)
This isn’t gold either, I am sure there are a lot other types of ways you can do this, we do this so it is much easier to find project, assemblies, and build the proper deployments. Plus when looking through your assemblies, seeing full names, rather than ‘MS.BLL.dll’ is a lot more friendly.