I was just wondering, why would somebody want to create multiple projects in one solution, if he could just as easily create a new solution for each project.
What are the best practices/arguments in deciding which setup is better?
Share
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 was just wondering, why would somebody want to create multiple projects in one solution, if he could just as easily create a new solution for each project.
What are the best practices/arguments in deciding which setup is better?
Multiple projects in one solution is very common. The norm even. It’s very rare an entire program can be captured in one project. A simple example is unit tests. You typically want those in their own project, but the same solution so they remain easily accessible.