Menu
We were thinking about organizing our BIG project this way:
\trunk [CompanyName] [Product1] [Project1] CompanyName.Product1.Project1.csproj [Project2] CompanyName.Product1.Project2.csproj CompanyName.Product1.sln [Product2]
We were trying to follow Microsoft's recommendation that namespace names follow folder structure, but are there any drawbacks for making it this way? What is the naming convention for solutions and projects that you apply?
403
File naming best practices:Avoid special characters or spaces in a file name. Use capitals and underscores instead of periods or spaces or slashes. Use date format ISO 8601: YYYYMMDD. Include a version number (Creamer et al.
What are project naming conventions? Quite simply it is the action of making sure that the same name, description or acronym is used to describe a project, process, etc. As opposed to using or interchanging names, etc.
That looks pretty good if you ask me. Especially naming your projects by their full name including full name space part. I've found this helpful when there are numerous projects, especially if there happens to be similar projects across different products.
How and whether you split on product and project (where I assume project is more like an application than a solution project) is very much down to the size of your organisation, it's make-up and your preferences.
63
An alternative that I've used is to have all my solution files in the same directory.
\trunk [CompanyName] CompanyName.Product1.sln CompanyName.Product2.sln [Product1] [Project1] CompanyName.Product1.Project1.csproj [Project2] CompanyName.Product1.Project2.csproj [Product2] [Project3] CompanyName.Product2.Project3.csproj
36
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
