Multiple projects within a solution: Interface naming convention
.net, c#
Solution
This is a common pattern for organizing solutions with many projects. However, there is some debate whether (in some cases) it is worth it.
I've seen a few different naming conventions used:
- Inc.Project.Contract
- Inc.Project.Contracts
- Inc.Project.Interface
- Inc.Project (like a base project that is a common dependency)
- Inc.Project.Common
Problem
I was wondering what the naming convention for an Interface sub project within a solution would be. I know interface files start with an "I", does this apply to projects as well? I have separated the interface into a separate project to keep the solution organised, as opposed to creating a interface file within the project which would be implementing the interface. All files and projects are contained within one solution. I apologise if this doesn't read well.