|
  
- Thread
- 25
- Credit
- 12
- Money
- 12
- Read Perm.
- 100
- Joined
- 30-12-2009
 
|
Post Last Edit by d2R at 9-2-2010 23:09
Post Last Edit by d2R at 9-2-2010 23:09
Version Control (aka Revision Control aka Source Control) lets you track your files over time. But why do you need it?
Large, fast-changing projects with many authors need a Version Control System (geekspeak for “file database”) to track changes and avoid general chaos. A good VCS does the following:
- Backup and Restore. Files are saved as they are edited, and you can jump to any moment in time. Need that file as it was on Feb 23, 2007? No problem.
- Synchronization. Lets people share files and stay up-to-date with the latest version.
- Short-term undo. Monkeying with a file and messed it up? (That’s just like you, isn’t it?). Throw away your changes and go back to the “last known good” version in the database.
- Long-term undo. Sometimes we mess up bad. Suppose you made a change a year ago, and it had a bug. Jump back to the old version, and see what change was made that day.
- Track Changes. As files are updated, you can leave messages explaining why the change happened (stored in the VCS, not the file). This makes it easy to see how a file is evolving over time, and why.
- Track Ownership. A VCS tags every change with the name of the person who made it. Helpful for blamestorming giving credit.
- Sandboxing, or insurance against yourself. Making a big change? You can make temporary changes in an isolated area, test and work out the kinks before “checking in” your changes.
- Branching and merging. A larger sandbox. You can branch a copy of your code into a separate area and modify it in isolation (tracking changes separately). Later, you can merge your work back into the common area.
Personally, if you need to use version control with Visual Studio, I recommend use the opensource product Ankhsvn along with TortoiseSVN .
for more info. check out the following link:
A Visual Guide to Version Control
http://svnbook.red-bean.com/
|
|