Apps are all about the code behind them… Every line of code written is like another stroke of an artist’s brush. Well thought out and designed code is like art and once you lay it down you don’t want to lose it. That’s why I never write a single line of code without being connected to some sort of source control system. I used to be a Build Engineer and my dad is a Configuration Management (CM) guru so I guess you could say it’s just in my blood.
This article is from a short series “My Windows 8 App Dev Week” so you may want to checkout the others as well.
- The Idea
- Keeping the Source Safe
TFS in the Cloud
Good CM and dev practices are about more than just source control and build process. It’s about integrated planning, development, test, etc. Having great infrastructure to support development, even in very small teams, is critical to DevOps. The more developers can just focus on building and designing systems the more amazing their creations can become.
One of the main promises of cloud is that an organization can focus on it’s core competencies instead of investing in the acquisition and maintenance of infrastructure. DevOps is no different which is why we’re building a cloud version of Team Foundation Server called Team Foundation Service.
This is built on top of Windows Azure and is integrated deeply with Visual Studio. You can also use Team Foundation Service with Eclipse and your programming language of choice.
Setting it Up
First thing to do is to sign up for a trial account. I did this months ago so I don’t have any detailed screenshots I can share right now.
Once have an account setup you need to create a new project.
Within seconds you will have a full blown enterprise-class Application Lifecycle Management (ALM) system up and running which is AWESOME!
Once you’re setup, as long as you already Visual Studio installed, the easiest way to get connected is launching Visual Studio right from the Team Foundation Service portal.
From there just make sure login with the same Microsoft Account that you used to setup Team Foundation Service.
That will automatically connect Team Explorer within Visual Studio up to Team Foundation Service. From there just launch the Source Control Explorer.
Now map a local path on your machine where you want to store your source code on your machine.
Now you’re good to go! You can use Source Control Explorer to manage code check ins and outs or you can bind your solution to Team Foundation Service and Visual Studio will prompt you.
Now Go Write Some Damn Code!
So… I guess I am a bit of CM geek. I never even do tutorials or write sample code without being connected to some sort of source control system. Now I can work from any of my machines and be confident that if my hard drive dies, I drop my laptop or spill carrot juice on the keyboard (all of which I’ve done in the past few months) my precious art (code) will be safe.
In this article I’ve only scratched the surface of the power of Team Foundation Service. I’ve used it on a couple of projects using Scrum over the past 9 months and it did exactly what it should which is just get out of the way of the development team being productive and help the team move fast and build great products.