VS 2010, Git and a multi-project solution

Question

Do I need to create a repository for each project, or only one that covers all projects in this solution?

Answer 1

It depends on whether you use a lot of common code through libraries or services. If you use libraries that you need for different versions, it's easier to separate them and use git submodules (via git slave, if you want). If you need libraries that will be the last for all projects (because they access the shared data store), you can be fine with one repo.

It might be easier for individual repositories to control access, but the hitolit is great because it can limit the branch and much more.

You can later join transplant repositories and transplant stories together through "git rebase --root --onto branch1". Or you can split one into many using git filter-branch.

So I wouldn't sweat too much. You are using git for some reason. You can change your mind later and save the story.

Answer 2

You can go anyway depending on your requirements, especially on how the projects are connected. If the projects are in the same repository, it is easier to add links between them. If they are located in different repositories, it is easier to have different access control settings.

If the projects are in the same solution, although you definitely need one repository.

Answer 3

I worked with Git with a very large set of projects (200+), in which the application was a group of main projects with a large number of connected projects. We used the Android Repo script (http://source.android.com/source/git-repo.html) to help them deal.

This was necessary for us, since we had a dozen or so plug-ins for different products. This is a pretty smooth tool. The main disadvantage is the lack of documentation for the repo and a terrible choice of name (not for searching).