Visual Studio GIT Save Branch as Solution
up vote
-1
down vote
favorite
Using a local GIT repository for C# code in Visual Studio 2017, and I've generated a few local branches. Is there any way to save a branch as a totally separate Visual Studio solution, unrelated to the other branches and histories?
Thanks.
c# git visual-studio
asked Nov 11 at 13:54
ebergerly
76
|
show 3 more comments
up vote
-1
down vote
favorite
Using a local GIT repository for C# code in Visual Studio 2017, and I've generated a few local branches. Is there any way to save a branch as a totally separate Visual Studio solution, unrelated to the other branches and histories?
Thanks.
c# git visual-studio
asked Nov 11 at 13:54
ebergerly
76
A git branch and a Visual Studio solution are two entirely different concepts. You can store a solution in a branch, but you cannot store a branch as a solution. You could copy the solution from branch A and import it to branch B however (perhaps after renaming). If you want a completely clean slate then start a new git repository.
– Ryan Pierce Williams
Nov 11 at 13:58
Thanks. I guess this gets back to what seems to be one of the most difficult issues in the software universe, which I've never quite understood: why can't you simply save a VS solution as a totally separate solution with a different name? You have all the info required to describe the branch/solution, so why can't VS simply save it under the name of the branch?
– ebergerly
Nov 11 at 14:03
The git tools you have in Visual Studio are just a plug-in to conveniently access a git repo. The repo has nothing to do with your solution, with your code - it is simply the place your code gets stored to. Often times you won't use git with Visual Studios at all. I've used at least 3 different repository solutions at my different places of work with Visual Studios.
– Ryan Pierce Williams
Nov 11 at 14:07
Thanks, but the git repository data in your local repository has all the data on history/changes to fully describe a VS solution, defined by the branch you're working on. Otherwise you couldn't open up a fully up-to-date branch as a full solution in VS, right? So if VS is using that data to give you what is effectively a branch solution, why can't it just save that? I'm sure that's up to MS and it's probably a rhetorical question, but geez it's so frustrating that VS doesn't allow you to "Save As" with your active solution.
– ebergerly
Nov 11 at 14:17
1
Visual Studios isn't built on git and doesn't directly rely upon any git data (though the git plugin for Visual Studios will use and interact with it). You are confusing the plugin for the main product.
– Ryan Pierce Williams
Nov 11 at 14:19
|
show 3 more comments
up vote
-1
down vote
favorite
up vote
-1
down vote
favorite
Using a local GIT repository for C# code in Visual Studio 2017, and I've generated a few local branches. Is there any way to save a branch as a totally separate Visual Studio solution, unrelated to the other branches and histories?
Thanks.
c# git visual-studio
asked Nov 11 at 13:54
ebergerly
76
Using a local GIT repository for C# code in Visual Studio 2017, and I've generated a few local branches. Is there any way to save a branch as a totally separate Visual Studio solution, unrelated to the other branches and histories?
Thanks.
c# git visual-studio
c# git visual-studio
asked Nov 11 at 13:54
ebergerly
76
asked Nov 11 at 13:54
ebergerly
76
asked Nov 11 at 13:54
ebergerly
76
asked Nov 11 at 13:54
ebergerly
76
asked Nov 11 at 13:54
ebergerly
76
76
A git branch and a Visual Studio solution are two entirely different concepts. You can store a solution in a branch, but you cannot store a branch as a solution. You could copy the solution from branch A and import it to branch B however (perhaps after renaming). If you want a completely clean slate then start a new git repository.
– Ryan Pierce Williams
Nov 11 at 13:58
Thanks. I guess this gets back to what seems to be one of the most difficult issues in the software universe, which I've never quite understood: why can't you simply save a VS solution as a totally separate solution with a different name? You have all the info required to describe the branch/solution, so why can't VS simply save it under the name of the branch?
– ebergerly
Nov 11 at 14:03
The git tools you have in Visual Studio are just a plug-in to conveniently access a git repo. The repo has nothing to do with your solution, with your code - it is simply the place your code gets stored to. Often times you won't use git with Visual Studios at all. I've used at least 3 different repository solutions at my different places of work with Visual Studios.
– Ryan Pierce Williams
Nov 11 at 14:07
Thanks, but the git repository data in your local repository has all the data on history/changes to fully describe a VS solution, defined by the branch you're working on. Otherwise you couldn't open up a fully up-to-date branch as a full solution in VS, right? So if VS is using that data to give you what is effectively a branch solution, why can't it just save that? I'm sure that's up to MS and it's probably a rhetorical question, but geez it's so frustrating that VS doesn't allow you to "Save As" with your active solution.
– ebergerly
Nov 11 at 14:17
1
Visual Studios isn't built on git and doesn't directly rely upon any git data (though the git plugin for Visual Studios will use and interact with it). You are confusing the plugin for the main product.
– Ryan Pierce Williams
Nov 11 at 14:19
|
show 3 more comments
A git branch and a Visual Studio solution are two entirely different concepts. You can store a solution in a branch, but you cannot store a branch as a solution. You could copy the solution from branch A and import it to branch B however (perhaps after renaming). If you want a completely clean slate then start a new git repository.
– Ryan Pierce Williams
Nov 11 at 13:58
Thanks. I guess this gets back to what seems to be one of the most difficult issues in the software universe, which I've never quite understood: why can't you simply save a VS solution as a totally separate solution with a different name? You have all the info required to describe the branch/solution, so why can't VS simply save it under the name of the branch?
– ebergerly
Nov 11 at 14:03
The git tools you have in Visual Studio are just a plug-in to conveniently access a git repo. The repo has nothing to do with your solution, with your code - it is simply the place your code gets stored to. Often times you won't use git with Visual Studios at all. I've used at least 3 different repository solutions at my different places of work with Visual Studios.
– Ryan Pierce Williams
Nov 11 at 14:07
Thanks, but the git repository data in your local repository has all the data on history/changes to fully describe a VS solution, defined by the branch you're working on. Otherwise you couldn't open up a fully up-to-date branch as a full solution in VS, right? So if VS is using that data to give you what is effectively a branch solution, why can't it just save that? I'm sure that's up to MS and it's probably a rhetorical question, but geez it's so frustrating that VS doesn't allow you to "Save As" with your active solution.
– ebergerly
Nov 11 at 14:17
1
Visual Studios isn't built on git and doesn't directly rely upon any git data (though the git plugin for Visual Studios will use and interact with it). You are confusing the plugin for the main product.
– Ryan Pierce Williams
Nov 11 at 14:19
A git branch and a Visual Studio solution are two entirely different concepts. You can store a solution in a branch, but you cannot store a branch as a solution. You could copy the solution from branch A and import it to branch B however (perhaps after renaming). If you want a completely clean slate then start a new git repository.
– Ryan Pierce Williams
Nov 11 at 13:58
A git branch and a Visual Studio solution are two entirely different concepts. You can store a solution in a branch, but you cannot store a branch as a solution. You could copy the solution from branch A and import it to branch B however (perhaps after renaming). If you want a completely clean slate then start a new git repository.
– Ryan Pierce Williams
Nov 11 at 13:58
Thanks. I guess this gets back to what seems to be one of the most difficult issues in the software universe, which I've never quite understood: why can't you simply save a VS solution as a totally separate solution with a different name? You have all the info required to describe the branch/solution, so why can't VS simply save it under the name of the branch?
– ebergerly
Nov 11 at 14:03
Thanks. I guess this gets back to what seems to be one of the most difficult issues in the software universe, which I've never quite understood: why can't you simply save a VS solution as a totally separate solution with a different name? You have all the info required to describe the branch/solution, so why can't VS simply save it under the name of the branch?
– ebergerly
Nov 11 at 14:03
The git tools you have in Visual Studio are just a plug-in to conveniently access a git repo. The repo has nothing to do with your solution, with your code - it is simply the place your code gets stored to. Often times you won't use git with Visual Studios at all. I've used at least 3 different repository solutions at my different places of work with Visual Studios.
– Ryan Pierce Williams
Nov 11 at 14:07
The git tools you have in Visual Studio are just a plug-in to conveniently access a git repo. The repo has nothing to do with your solution, with your code - it is simply the place your code gets stored to. Often times you won't use git with Visual Studios at all. I've used at least 3 different repository solutions at my different places of work with Visual Studios.
– Ryan Pierce Williams
Nov 11 at 14:07
Thanks, but the git repository data in your local repository has all the data on history/changes to fully describe a VS solution, defined by the branch you're working on. Otherwise you couldn't open up a fully up-to-date branch as a full solution in VS, right? So if VS is using that data to give you what is effectively a branch solution, why can't it just save that? I'm sure that's up to MS and it's probably a rhetorical question, but geez it's so frustrating that VS doesn't allow you to "Save As" with your active solution.
– ebergerly
Nov 11 at 14:17
Thanks, but the git repository data in your local repository has all the data on history/changes to fully describe a VS solution, defined by the branch you're working on. Otherwise you couldn't open up a fully up-to-date branch as a full solution in VS, right? So if VS is using that data to give you what is effectively a branch solution, why can't it just save that? I'm sure that's up to MS and it's probably a rhetorical question, but geez it's so frustrating that VS doesn't allow you to "Save As" with your active solution.
– ebergerly
Nov 11 at 14:17
1
1
Visual Studios isn't built on git and doesn't directly rely upon any git data (though the git plugin for Visual Studios will use and interact with it). You are confusing the plugin for the main product.
– Ryan Pierce Williams
Nov 11 at 14:19
Visual Studios isn't built on git and doesn't directly rely upon any git data (though the git plugin for Visual Studios will use and interact with it). You are confusing the plugin for the main product.
– Ryan Pierce Williams
Nov 11 at 14:19
|
show 3 more comments
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53249443%2fvisual-studio-git-save-branch-as-solution%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
A git branch and a Visual Studio solution are two entirely different concepts. You can store a solution in a branch, but you cannot store a branch as a solution. You could copy the solution from branch A and import it to branch B however (perhaps after renaming). If you want a completely clean slate then start a new git repository.
– Ryan Pierce Williams
Nov 11 at 13:58
Thanks. I guess this gets back to what seems to be one of the most difficult issues in the software universe, which I've never quite understood: why can't you simply save a VS solution as a totally separate solution with a different name? You have all the info required to describe the branch/solution, so why can't VS simply save it under the name of the branch?
– ebergerly
Nov 11 at 14:03
The git tools you have in Visual Studio are just a plug-in to conveniently access a git repo. The repo has nothing to do with your solution, with your code - it is simply the place your code gets stored to. Often times you won't use git with Visual Studios at all. I've used at least 3 different repository solutions at my different places of work with Visual Studios.
– Ryan Pierce Williams
Nov 11 at 14:07
Thanks, but the git repository data in your local repository has all the data on history/changes to fully describe a VS solution, defined by the branch you're working on. Otherwise you couldn't open up a fully up-to-date branch as a full solution in VS, right? So if VS is using that data to give you what is effectively a branch solution, why can't it just save that? I'm sure that's up to MS and it's probably a rhetorical question, but geez it's so frustrating that VS doesn't allow you to "Save As" with your active solution.
– ebergerly
Nov 11 at 14:17
1
Visual Studios isn't built on git and doesn't directly rely upon any git data (though the git plugin for Visual Studios will use and interact with it). You are confusing the plugin for the main product.
– Ryan Pierce Williams
Nov 11 at 14:19