"Melissa Roberts" <bi*******@micr osoft.com> wrote in message
news:uJudnSKjNb eZKircRVn-
How do you guys/gals keep track of changes in your software? How do you
revert to an older version if the new one gets out of control?
What I do is every version that works I create a new folder named
VerName++ and save there so I can revert back to it if needed. There has to be a
better way to do this. Please advise.
The VerName folder method is good. After all, we may want to use the old
version code to read a file in the old format, and then save it to the new
format using the new version code. So all of the code should be accessible.
We should also consider using namespaces to partition the code. Right now
I'm still learning the ways to do this, so don't know much about it at
present.
As for keeping track of old versions of the code, merging patch fixes into
different code lines in order to support customers on different code lines,
the best way seems to be to use 3rd party versioning tools as others have
pointed out. There are many other packages other than the big three
mentioned in EventHelix.com' s reply. Just do a search in the internet.