Geek asks and answers

Great solution for Visual Studio

I have a solution for my web application with almost 12 projects and 3 websites. There are several projects that I use for several websites, such as MyProject.BE/MyProject.BLL/MyProject.DAL/MyProject.Controls projects.

My question is: is it good to have several projects for BE / BLL / DAL / Controls, is it better to create 1 project with folders for BE / BLL / DAL layers?

+5
source share
3 answers

The question of "big" is relative. Software development is mainly about how good your computer is. If you can compile and run 100 projects in 1 second, then 100 projects in the solution are "small." So this is really a question of what works for you.

My current working solution has about 130 projects. Yes, we could break it, but we have some impressive boxes that can handle this, so the cost of having 130 projects is moderate to low and the benefits are more than the costs.

- , , . Darn..., , "", . ( ), . , .

: " , ".

. .

+6

, . , , WinForms, BE DAL-, , , WinForms.

0

, ---, --I-make-- --VS-open -my-code-, ?

, , , , . "BE/BLL/DAL/Controls", .

, . , . , , , . , .

, , .

, ? . , ? , SRP .

Microsoft Press: Windows Presentation Foundation Model View ViewModel Pattern

, .

Another suggestion on how to structure the solution is in this SO thread: Mvvm applications and business layer location

0
source

More articles:


All Articles