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’ve got a solution for my webapplication with almost 12 projects and 3 websites.
There are some projects that I use for multiple websites like MyProject.BE / MyProject.BLL / MyProject.DAL / MyProject.Controls projects.
My question is, is it good to have multiple projects for BE/BLL/DAL/Controls, of is it better to create 1 project with folders for the BE/BLL/DAL layers?
The question of “large” is a relative one. In software development it is mostly a question of how good your PC is. If you can compile and run 100 projects in 1 second then 100 projects in a solution is “small”. So it is really a question of what works for you.
My current work solution has about 130 projects in it. Yep, we could break it out but we have got some impressive boxes that can handle this so the cost of having 130 projects is moderate to low and advantages are bigger that the costs.
Having all of the projects in one solution is the go if you can compile, run, & test them all quickly. Darn … that then starts the conversation onto what is “quick” and that is a style question. If you compile and run tests often (every minute or faster) then quick is seconds. If you compile and run every hour or so then minutes would be okay.
Answer: “Do what works for you”.
Note: Consider solution folders.