Developing with Source Code Control Best Practices Part 1

re: Developing with Source Code Control Best Practices Part 1

PeterRitchie — Sat, 25 Oct 2008 12:25:43 GMT

Assam, choose SVN over Visual SourceSafe.

re: Developing with Source Code Control Best Practices Part 1

Assam Zafar — Sat, 25 Oct 2008 11:29:45 GMT

Along with this article it would really be very helpful if the guys reading this post also rate their Source Code Control(w.r.t the article). This would eventually help new developers like me to select the best tools available for enforcing standards.

I have used SVN and Visual Source Safe. To me SVN is the best amongst the both.

Weekly Link Post 64 « Rhonda Tipton’s WebLog

Weekly Link Post 64 « Rhonda Tipton’s WebLog — Sun, 19 Oct 2008 20:39:14 GMT

Pingback from Weekly Link Post 64 « Rhonda Tipton’s WebLog

re: Developing with Source Code Control Best Practices Part 1

Jeroen Eikmans — Sun, 19 Oct 2008 10:12:28 GMT

@Jonathan: I think Peter uses shelving to facilitate private branching. At least I do with SVN.

re: Developing with Source Code Control Best Practices Part 1

Richard Dingwall — Sun, 19 Oct 2008 09:43:10 GMT

> Check in related changes atomically.

This also helps when reviewing other people's changes - if it's all in one changeset, you don't have to re-trace their steps to find out all the things they modified.

These are pretty basic tips, but they're easy to miss for source control newbies. Once you've got source control going, there's often little time spent on learning to use it effectively (beyond basic check in/check out). They're important though - this stuff should be right up there with writing meaningful comments in your code. Good write up!

re: Developing with Source Code Control Best Practices Part 1

Usman Masood — Sun, 19 Oct 2008 02:46:55 GMT

SCC is a really nice option in professional envoirnment... it saves you from lots of troubles..

2ndly try Microsoft Team Foundation Server... it also allows to define policies which can prevent such things.

re: Developing with Source Code Control Best Practices Part 1

Juan Cherry — Sun, 19 Oct 2008 00:24:24 GMT

I have been a hobbyist programmer for 10+ years and have never attempted to use SCC. I think I will give it a shot. Nice article.

re: Developing with Source Code Control Best Practices Part 1

Jonathan Allen — Sat, 18 Oct 2008 23:33:01 GMT

> Never check in changes that cannot be built.

That recommendation suggests to me that you are using a seriously under-powered source control system.

A good SCC will allow you to check in your work in progress no matter what state it is in without exposing those changes to the whole world.

Take a look at AccuRev or ClearCase, which make creating private branches and moving changes form branch to branch a trivial operation.

Developing with Source Code Control Best Practices Part 1

DotNetKicks.com — Sat, 18 Oct 2008 14:00:19 GMT

You've been kicked (a good thing) - Trackback from DotNetKicks.com