- VISUAL STUDIO PACKAGE MANAGER CONSOLE GIT INSTALL
- VISUAL STUDIO PACKAGE MANAGER CONSOLE GIT CODE
- VISUAL STUDIO PACKAGE MANAGER CONSOLE GIT DOWNLOAD
Test drive (or, randomly clicking around to see what jumps out at me) Fast, lightweight installs are quite nice, and I like that I can disable or uninstall them without fear of setting the house on fire.
I, for one, welcome our new VSIX overlords. It installed in maybe 15 seconds - if that. I expected this to be a little faster since it's a VSIX, but it was so fast I didn't get screenshot. Next up was the the Visual Studio Tools for Git extension. Not crazy fast, but barely long enough for me to get a cup of coffee.
VISUAL STUDIO PACKAGE MANAGER CONSOLE GIT INSTALL
The Visual Studio 2012 Update 2 install took 8 minutes for me and didn't require a reboot - make sure you've got Visual Studio closed when installing the update, of course. VS2012.2, just shipped and has a lot of nice new features (even a blue theme for the nostalgic). Note: In case you missed it, Visual Studio's moved to delivering regular updates (with new features) on a shorter delivery interval.
VISUAL STUDIO PACKAGE MANAGER CONSOLE GIT DOWNLOAD
I think the download page could be a little more clear - I figured I'd start with the smallest one and it worked on my machine. I already had Visual Studio 2012 installed, so step one was installing Visual Studio 2012 Update 2 CTP. The big Getting Started with Git in Visual Studio and Team Foundation Service post has a Get set up note at the top that worked great for me. Installing the Git tools for Visual Studio 2012 Oh, and it works with Visual Studio Express, too.
VISUAL STUDIO PACKAGE MANAGER CONSOLE GIT CODE
Tl dr: It doesn't mess with my code or project files, works well distributed, and integrates cleanly with stuff like. I didn't read them, partly because it looked like a lot of work, and partly because I wanted to see if I could just click around and good things would happen. I think of code as files, not a bunch of stuff living in Visual Studio, and I want to manage it.ĭisclaimer: There are a lot of good posts about the new Git support in Visual Studio 2012 with lots of nice pictures. It's nice to see file status, history, merges, etc., but I didn't want it locking my files or messing with my project files or. I wasn't sure I'd like GitHub support in Visual Studio, though. If nothing else, GitHub for Windows takes the annoyance thinking about SSH keys out of the picture.
removing files, merging, git deploy to Azure). I've found that the GitHub for Windows client works pretty well for a lot of day to day work, and I can quickly pop open a shell window when I need it (e.g. Some people will make fun of you if you don't use the command line in git and it's true that the old git windows tools weren't very useful. I've been using GitHub for Windows app a lot since it was released. I quickly decided that msysgit wasn't helpful, bounced between the command line and Visual Studio for a while, then used the git command line in the Visual Studio Package Manager console. I've used the command line, posh-git, and GitHub for Windows (you knew you can use GitHub for Windows with non-GitHub repositories, right?). I've got several public and private repos on CodePlex, GitHub and BitBucket - open source projects, book sample code, presentation content, etc. My team uses it exclusively for internal work, collaboration with vendors, and public open source releases.
0 kommentar(er)
