This is really important, and however it is done it needs
to be robust and reliable. Renaming is probably a bit
easier than moving. Even if when you open a file in
VS.NET and the CheckPoint add-in can't find the
checkpoint version history then it should prompt to
create a new one or browse for another. If it browses
for another then it should automatically rename the one
found to match any CheckPoint file naming conventions
(e.g. Source.cs.checkpoint) and prompt to remove the
other one.
Log in to post a comment.
