Click here to Skip to main content
15,884,177 members
Please Sign up or sign in to vote.
3.00/5 (1 vote)
See more:
I am trying to set up a GIT repository for a system we are developing. I desire a single repository, but want to separate the front end applications from the back end services by solutions in .NET. I want to be able to pull the front end code and the back end code separately.

I tried to email the GIT team per the GIT web site at http://git-scm.com/community. The email address is git@vger.kernel.org. Unfortunately, my plain-text email was rejected by the site.

Is there anyone out there that has successfully set up a git repository like my needs?
Posted

You're not being really clear on how this code is managed when you develop it, but I am presuming you are using Visual Studio 2013 and want to add both solutions under the same git repo.

Short answer is, that can't be done. Not if you are going to manage your code in Visual Studio 2013, anyway. 1 solution = 1 repository, always.

In that way, git handling in VS is different than had you used TFS, which allows you to manage code by workspaces. Git uses a different assumption.

That said, there's no harm in having two different repos. Since that's the way you treat the project, it makes sense to have different repos.

However, if you MUST have both solutions in the same git repo, the way you would do that is to not use VS to manage the source control. Instead, you would put both solutions in the same parent folder.

Then you would apply git source control to that parent folder using a third-party tool, such as SourceTree.

This would require you to use SourceTree or the like to manage your commits and remotes, and would become unwieldy if you have a lot of people working on the same repo. But it is doable.

My best advice: Just use two different repos. That's your development pattern, anyway. Don't tamper with success.
 
Share this answer
 
GIT repository has nothing special to do with VS Solutions. A GIT project is just the directory with all its inner content (roughly speaking), and the Revision Control System (not only GIT) tracks each and every essential change in this directory (some files can be filtered out as unrelated, such as non-source files). That's all. Inside, you can have any number of solutions and solution directories, projects and project directories, anything.

Look, isn't it obvious: Revision Control System should be kept agnostic to the content of files and directories, and the programming entities, program directories, files, and other project artifacts, should be agnostic to the procedures of tracking their sources, behaving as if there was only one version?

—SA
 
Share this answer
 
Sergey

I appreciate your response. Our team is new to GIT and we don't know how to set pulls to get a subset of the repository. Can you give us some help? The repository is not public facing.

Thanks

Tom
 
Share this answer
 

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900