VS Git
-
I'm not sure if this is by design, or a bug. I created a new WPF project & solution. I added 4 previously existing projects, which all have their own repos, to the solution. I then added a couple of new class library projects to the soltion. When I open the Git window, it shows the 4 previously existsing repos, but there is no repo for my new app. How do I add my new solution, WPF project, and class library projects to Git using VS? If I remove the 4 pre-exising projects, and close & reopen the solution, then there is an menu option to create a repo for it. But then I have broken refs and have to fix those & commit. This can't be right. What am I doing wrong here?
In theory, theory and practice are the same. But in practice, they never are.” If it's not broken, fix it until it is. Everything makes sense in someone's mind.
-
I'm not sure if this is by design, or a bug. I created a new WPF project & solution. I added 4 previously existing projects, which all have their own repos, to the solution. I then added a couple of new class library projects to the soltion. When I open the Git window, it shows the 4 previously existsing repos, but there is no repo for my new app. How do I add my new solution, WPF project, and class library projects to Git using VS? If I remove the 4 pre-exising projects, and close & reopen the solution, then there is an menu option to create a repo for it. But then I have broken refs and have to fix those & commit. This can't be right. What am I doing wrong here?
In theory, theory and practice are the same. But in practice, they never are.” If it's not broken, fix it until it is. Everything makes sense in someone's mind.
You'll have to create a new repository for the new application. File->New->Repository
The difficult we do right away... ...the impossible takes slightly longer.
-
You'll have to create a new repository for the new application. File->New->Repository
The difficult we do right away... ...the impossible takes slightly longer.
That created a new repo ib Git, but nothing appears local. The remote has no files in it either. [UPDATE] You have to set the Local Repository path. It sets it My Docs, which created an empty repo there. Once I changed it to my app's directory, it worked fine. Thanks
In theory, theory and practice are the same. But in practice, they never are.” If it's not broken, fix it until it is. Everything makes sense in someone's mind.
-
I'm not sure if this is by design, or a bug. I created a new WPF project & solution. I added 4 previously existing projects, which all have their own repos, to the solution. I then added a couple of new class library projects to the soltion. When I open the Git window, it shows the 4 previously existsing repos, but there is no repo for my new app. How do I add my new solution, WPF project, and class library projects to Git using VS? If I remove the 4 pre-exising projects, and close & reopen the solution, then there is an menu option to create a repo for it. But then I have broken refs and have to fix those & commit. This can't be right. What am I doing wrong here?
In theory, theory and practice are the same. But in practice, they never are.” If it's not broken, fix it until it is. Everything makes sense in someone's mind.
Kevin Marois wrote:
I added 4 previously existing projects, which all have their own repos, to the solution.
If you change two files in two of those repos how are you going to handle checkins? How are you going to insure that if you need to rebuild a delivered laydown (one or more binaries) that you will be able to reliably reproduce the original binary?
Kevin Marois wrote:
What am I doing wrong here?
Not managing Git as intended? A git repo is a deliverable. So your new project should be using 4 deliverables not 4 repos. Each repo should be independently worked and then a binary is released. With a version number. Your project uses the binary and specifies it via the version number. In contrast there are other version control systems that allows one to manage deliverables from one single location. You can, for example, independently label parts of those any way you want. And then combine into another deliverable either by combining labels or just take the tip of everything. You can even label individual files. But other than that as others have mentioned you need a new repo.
