I am using Visual Studio 2010 Express. I know that this edition does not support git extensions integration. So I have tried a standalone source control Gui like git extensions but today I have seen another possibility that is GitHub for Windows.
I would like to know which is the difference between Git extensions and GitHub for Windows.
As illustrated here, GitHub for Windows (G4W) can interface with only the latest version of Visual Studio.
This is the main difference, in the context of your question, with Git Extensions, which is a plugin for Visual Studio (2005/2008/2010/2012), as shown in this article.
As such, Git Extensions isn't a "stand alone GUI".
You would compare, for "stand alone" GUIs, a G4W and an Atlassian Stash for instance.
I ran into the same question. Maybe this will help the next person.
Git for Windows - is a lightweight, native set of tools that bring the full feature set of the Git SCM(source control management software) to Windows while providing appropriate user interfaces for experienced Git users and novices alike. (source)
This tool can also be installed separately by visiting https://git-for-windows.github.io. This tools is not just for github but for git in general.
GitHub Extensions for Visual Studio - "lets you connect to GitHhub.com or GitHub enterprise and work with GitHub repositories inside of the visual studio IDE." (source: MS help) It adds a functionality(like context menus) inside of Visual Studio for things like creating and cloning repositories. (more here)
Git for windows lack lot of must have feature. gitextensions is most powerful GUI I ever use. Go for https://code.google.com/p/gitextensions/
Related
I have tried to install the GitHub pull and request extensions in the Visual Studio Code.I installed it. But when I searched "Github" in the Visual Studio there is nothing showing in the visual studio code.
Your question is not clear, but I will try to answer it based on my understanding.
Try with Ctrl+Shift+P and search git, you should see all git commands.
From the official website:
To get started with the GitHub in VS Code, you'll need to install Git, create a GitHub account and install the GitHub Pull Requests and Issues extension.
Once you've installed the GitHub Pull Requests and Issues extension, you'll need to sign in.
After this, you can search for and clone a repository from GitHub using the Git: Clone command in the Command Palette (Ctrl+Shift+P) or by using the Clone Repository button in the Source Control view (available when you have no folder open).
According to this:
VS Code ships with a Git source control manager (SCM) extension
However, I can't see Git in my latest version of Code. Neither can I see it under "Install Additional SCM Providers...".
I tried putting the path to my own Git client but it still does not show:
What is needed to enable Git in Code?
I fixed the same issue on my Mac by disabling all plugins and enabling them again.
I have a Visual Studio Code project for an Angular2 app created using AngularCli (webpack version). Out of the box, AngularCli will generate a new project for you and check it into Git. How do you know which GitHub account it's using? I cannot find any information in Visual Studio as to what GitHub account is controlling the code history. I can make changes to the code and check it in using Visual Studio Code's embedded Git functionality. I've logged into GitHub using my account, but I do not see this new project. Where do you find information on what GitHub account either AngualrCli and/or Visual Studio Code is using?
How do you know which GitHub account it's using?
It doesn't need to use any github account to create a git repo. It's just calling git init, followed by some git add/git commit commands. You can do those without github credentials. After the tool does its job, you have a fully-functional local git repo.
You only need github account when you try to push code to github, which you did not yet do, I assume. You don't need github credentials to work with local repository (view history, add new commits, branch, merge, etc.)
The canonical question on 'how to use Git in Visual Studio?' appears to be this one posted by Herb Caudill.
One of the more recent answers notes (correctly) that "Visual Studio 2013 natively supports Git".
So when I go to a Github page (supercolider's is the one I'm trying to clone) and click on the 'Clone in Desktop' button I would expect (hope) that Visual Studio 2013 would take up the link and clone the repository. That is not what happens, instead Windows (I'm using 8.1) asks me if I would like to visit the store to find an app that can handle files of type (github-windows).
What is the correct way to clone a GitHub repository in Windows under Visual Studio 2013? The various MSDN pages (e.g. Share your code in Git or Setup Git on your dev machine) mention GitHub but do not explain how to use it.
It is super easy once you know how :)
From within Visual Studio 2013:
Select File -> Open -> Open From Source Control
The Team Explorer window will come up, one of the sections is "Local GIT repositories". In that section choose "Clone".
That will bring up a path selection textbox and directory browser. Simply replace the default path with the git URL (in your case "https://github.com/supercollider/supercollider")
Thats it!
Note: unless specified otherwise, Visual Studio will store the actual files here:
C:\Users\\Source\Repos\
What you do is go to the Team Explorer, click the Connect to Team Projects, select the Clone option and enter the URL of the Repo you wish to clone and press Clone
To expand on neo12's answer & address the canonical question "how to use Git in Visual Studio"
I agree with neo12. Additionally you can also navigate directly to solutions from the Team Explorer "Local Git Repositories" section by double clicking them
Here is a walk through I put together to explain in concise detail. The video is less than 2 minutes. Let me know if this helps.
http://prestoasp.net/lesson/how-to-work-with-visual-studio-github/
Recently I tried out the new TFS-Service, and really liked the built in Scrum template for project management, and the new ability to create a team project managed with Git.
It would seem that the Git integration is only possible when using Visual Studio on windows though. Using Eclipse (with the Team Explorer plugin) I was unable to work with a git-based team project.
Is this really the case?
Heres what I've tried:
In TFS Service, I have a git-based team project with some commits in it.
In Eclipse, I connected to the team project, but it seems I can't pull or even see the source in any way. Source control explorer doesn't show any code (or any paths even).
In TFS, I created a new git-based team project. In Eclipse I created a new project and used Team -> Share... to try and get the code into TFS. But selecting TFS there doesn't seem to have the disired effect: it doesn't understand that it's a git-based team project, and so it doesn't try to push the code with git, but upload it to a new path ($/some/path/here/).
So is that it, or perhaps there's a workaround? Maybe I did something wrong?
BTW - I know about using TFS with git-tf, and I'm OK with that option, but it's not what I'm asking.
Thanks.
We're working on improving this for the next major version of Team Explorer Everywhere (TEE), but this is what you'll want to do today.
Eclipse already has a full featured Git version control provider in the eGit plugin. This is installed in many versions of Eclipse but if you do not have it you can install it from here:
http://marketplace.eclipse.org/node/1336
To use eGit today against the hosted service you must enable alternate credentials in TFS (click on your name in the top right corner, My Profile, Credentials then enable and configure your credentials).
Once this is enabled you can point eGit at your service account repo and you are good to go. In the Import or Share wizards pick Git and then follow through th eGit dialogs.
When you make a commit, if you add #123 into the work item comment it will associate the commit with that work item number when you push it to the server.
Now, I mentioned that we are trying to make this better. What we are aiming to do is show you both your TFVC and your Git related projects when you import and share and if you have picked a Git repo then we'll help you get your credentials set up, clone it and get the version control parts of Eclipse hooked up to eGit (assuming you have eGit installed). We'll also make sure that the other Team Explorer Views (such as work items, builds etc) all work great and that links to Git commits etc do the right thing. Hope that makes sense - but if anyone wants to talk more about how Git projects will work in future versions of Team Explorer Everywhere then feel free to drop me a mail (martinwo#microsoft.com)