VS 2010, Git, and a Solution with Multiple Projects

git

Solution

It depends if you are using a lot of shared code via libraries or services. If you are sharing libraries that you need to have at different versions, it's easier to separate them and use git submodules (via git slave, if you like). If you need the libraries to be the latest for all projects (because they access a common data store) you may be ok with one repo.

Separate repos may be easier to do access control, but gitolite is great as it can restrict by branch and many other things.

You can later join repositories and graft histories together via "git rebase --root --onto branch1". Or you can split one into many with git filter-branch.

So I wouldn't sweat it too much. You're using git for a reason. You can change your mind later and still keep the history.

Problem

Original source