Git

I was very excited to see that after several months of work Phil and Paul finally released their much talked about GitHub client for Windows. It has a great Metro style, and is very fluid and functional. Here is an example of what my client looks like As you can see it is very clean, and there are no typical windows borders or title bar which is common for Metro styled apps. As I was exploring the app, I stumbled on the fact that if you are using PowerShell as your default shell. ...

After reading Scott Hansleman’s post about Console2 I decided to give it a try full time. Overall I have to say I am very impressed and have no intention on switching back. It really is an impressive application, so if you are interested in trying something different, go to Scott’s post and follow his directions on setting it up. As a long time mysysgit user for all my Git source control needs, I decided to find out if I could marry the two together to create a nice intersection between Console2 and msysgit’s Bash client. And after a bit of searching and stumbling on my own post about setting up the bash client in Visual Studio, I answered my own question on how to set it up for Console2. Here is what I cam up with: ...

NuGet 1.6 was released today. And with it came some great new features, one that I am particularly excited about is. Using NuGet Without Checking In Packages (Package Restore) NuGet 1.6 now has first class support for the workflow in which NuGet packages are not added to source control, but instead are restored at build time if missing. For more details, read the Using NuGet without committing packages to source control topic. ...

I have been using GIT for about a year now, and over the last year I have configured some things in GIT that make my life as a developer much easier. This post is going to show you my .gitconfig and hopefully accelerate your own configurations of GIT. Finding the .gitconfig file Note: all of this below assumes you are using msysgit. If your are not using msysgit, your mileage may vary. ...

If you are an avid Git user like I am, but also happen to work in a Visual Studio environment, you know that getting to your Git Bash command prompt is anything but easy. My typical process looks probably something like yours: Open Visual Studio Open your project you are working on Right click on a folder in the project and choose “Open Folder in Windows Explorer” Back your way up through the folders in Windows Explorer till you get to the parent folder that is the root of your project. Then right click on the root folder of your project and choose “Git Bash Here” Start using Git Bash To me this process got so annoying and tedious that I finally decided to explorer other options to get to my Git Bash prompt. The best one that I have come up with so far and works perfectly for me is adding the Git Bash as an “External Tool” in Visual Studio. To get started you will need a couple of things: ...

I have heard a lot of chatter on blogs and twitter about how people just don’t get git. They exclaim it is too hard to learn, too hard to work with, doesn’t make sense, and on and on… To put this bluntly, I think they are just complaining for the sake of complaining, or at the very least they never bothered to learn how to use git. So as a remedy to this, I am publishing the only 6 git commands that you really need to know to get yourself started for a project where you are the sole-developer. ...

I wanted to post this mostly for my future reference. But I think it is also equally as useful to anybody else with a .NET project that is using the Git as their source control, and want to make sure non-code extras that come with .NET projects don’t get checked in. .gitignore File This file specifies the paths and files to ignore in your project. Each line constitutes a new path, and each one can use basic RegEx to generalize the ignore checking. ...