I have a visual studio solution with some (about 20) projects. The git control source is used for this solution.
This project is built around an existing application server (closed source, binary only). The application server consists of 300 files / 140 mb. The version of the application server can change 6 times a year (if new functions / corrections are needed) The developer needs this application server for testing (integration tests) development.
Most of these projects have links to some builds of this application server (i.e., to establish a connection). There are about 15 files for which we create NuGet packages that are hosted by ourselves.
Some projects may have links to official nugget packages.
In some projects, there may be links to 3rd-party assemblies, which are located in the "lib" folder and are part of the solution. The lib folder is also included in the git repository.
Question:
Where and how should we put application server files?
Version 1:
Paste the application folder next to the lib folder and add it to the git repository.
- Pro: the developer can simply check git and is ready to launch the server application. The developer can work offline.
- Cons: a lot of binaries in the git repository. As a result, a huge git repository will appear.
Version 2:
Put the robocopy script in the post build message and copy the application server after a successful build from a network resource or the Internet.
- Pro: a developer can just git check, build a solution and is ready to start the application server. The git repository will remain light.
- : /,
post build , , ,
. ,
,
.
?
/ , ?