All geek questions in one place

Recommendations on the organization of the structure / work "build" on a big solution

I am making a very large web application (currently in 70 projects and 150k loc, but with much more to do).

I use FinalBuilder to run build scripts. However, what are the best methods for structuring such a large project? What about build dependencies? What impact does the structure of my projects have on code performance (if any)?

I have seen some previous topics about this, but I cannot find them. I saw topics about solutions in excess of 600 projects in the solution, for the sake of clear answers, suggesting that this system will grow to such a size (I would like to know how to organize a project that is larger than my end, as that would mean that I can arrange a smaller solution).

If that matters, the system is mainly used in .NET 3.5 (C #, LINQ, SQL Server, etc.), but will also use Python / Erlang.

+3
source share
3 answers

I have only 40 projects (but several million loc), and the main best practices:

  • identify dependencies between projects
  • establish a global list of tags used by all projects wishing to participate in the next version.
  • make sure that every project that wants to publish its own shortcut in this global list has made this shortcut from the configuration (list of labels) coming from the global one.
  • register the "officials are building" (the one that can be deployed into production) in the repository.

Thus:

  • , ( ).
    , ( , ).
  • ( ) (, -,...)
  • ( ) .

:

  • .
  • ( script)
  • ( )
  • / ( , : , )

:
( ), (, , )

+3

NMaven 70 ? , , . , (, NUnit , ).

, .

+2

. , ,

  • Build Dependencies - , .
  • - LIB, DLL,...
  • -

  • Database - schemes, scripts, source data
  • General
  • Web
  • NTServices
  • Services - REST / SOAP Services
  • BizTalk - You Name Product-Specific Things
+1
source

Source: https://habr.com/ru/post/1708740/

More articles:


All Articles