Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a solution currently with a single project and multiple directories.
I was wondering whether there is a benefit to splitting these up into multiple projects instead?
No benefit, not from the description you have provided.
You will only add to the compilation time and deployment complexity.
Each project would end up compiling to a different DLL and the different projects will need to be referenced by each other (I think this is a safe assumption).
If you do need to deploy different portions of your codebase separately, then by all mean, split into multiple assemblies, but don’t do it to “organize” your code.