VISUAL STUDIO 2012 GIT CODE
VISUAL STUDIO 2012 GIT WINDOWS

VISUAL STUDIO 2012 GIT WINDOWS

On the Windows platform, git has several options for managing your code: вЂ“ ItвЂ™s lightweight to set up, powerful, and fully embraces the вЂњofflineвЂќ mode of working rather than the вЂњif-your-network connection-is-slow-then-VS-will-run-like-a-dogвЂќ way that TFS operates, which I nowadays find very frustrating. Overall, having used git, I must say that I do like the features it offers and the possibilities for helping teams of developers improve their day-to-day processes. Once I lost a couple of hoursвЂ™ work вЂ“ not much fun. Secondly, IвЂ™ve had one or two issues when IвЂ™ve somehow completely trashed my local repository, forcing me to completely clean the repository and вЂњstart overвЂќ. This is all very nice, although I have also struggled with some aspects of git вЂ“ firstly it blends concepts like merging and check-ins, so thereвЂ™s a slight learning curve there, as well as introducing the idea of вЂњrebasingвЂќ вЂ“ which essentially is the merging of two branches into one so that they appear as though they were a single set of ordered check-ins. In fact, itвЂ™s so easy to do you might be surprised by it at first вЂ“ you rollback or switch branches, and VS instantly says that files have been changed and updates.

VISUAL STUDIO 2012 GIT CODE

Git also performs quickly вЂ“ check-ins happen pretty much instantly as they are local, and you can instantly switch back to an older revision of code with a single command вЂ“ no complicated rolling back and so on. Oh, and there is no support for a вЂњsingle check outвЂќ mode like you have with TFS вЂ“ hopefully those days are beyond all of us! You can do things like perform multiple local check ins, and then before pushing to the remote repository, convert those many check-ins into one check-in.Д«ecause branches are much easier to control in git, you may find yourself doing things like feature branches more often. It also encourages more frequent checkins since youвЂ™re doing things locally, so part of the вЂњmental blockвЂќ of checking in centrally is removed. This means that you can do things like rollbacks, checkins, branches and merges all locally вЂ“ when youвЂ™re happy with your changes as an entire piece of work you can вЂњpushвЂќ the lot in one go to your remote repository (remote repository = TFS / SVN-style central source control server, although with git it doesnвЂ™t quite work like that). There are many reasons for this I think вЂ“ the biggest one is the fact that when you pull down code, you pull down the entire repository i.e. Branching is much easier to do than with other source control systems that IвЂ™ve used вЂ“ IвЂ™m talking TFS, SVN (and I suppose SourceSafe as well). Pretty much like everyone else, I imagine. Everyone is using it, and looking for any excuse to blog today, I wanted to share both my early experiences with it, and the new Microsoft git plugin for VS2012.

Git seems to be everywhere these days doesnвЂ™t it.

Visual studio 2012 git