My 10 cents:
This might work for Mirror or Update syncs, but can/will not work for Two-way or Custom syncs.
You would then have identically names different versions scattered around your sync locations.
What is wrong with the present versioning options?
request:versioning file path
- Posts: 2451
- Joined: 22 Aug 2012
- Posts: 2451
- Joined: 22 Aug 2012
I suppose your Version1 is your own way of managing versions in your projects.
The most common use of FFS is to have a source-location,
e.g. C:/BLABLA/Project
that is synced to a mirror-location
e.g. domain.sharefolder/BLABLA/Project
and use Versioning in the time-stamp [File] format in a versioning location
e.g. domain.sharefolder/BLABLA/ProjectVersions
After running a sync, you can then find the latest mirror of C:/BLABLA/Project in
domain.sharefolder/BLABLA/Project
in the identical (sub)folder structure as in C:/BLABLA/Project
and any previous versions in
domain.sharefolder/BLABLA/ProjectVersions
again in the identical (sub)folder structure as in C:/BLABLA/Project and domain.sharefolder/BLABLA/Project
The most common use of FFS is to have a source-location,
e.g. C:/BLABLA/Project
that is synced to a mirror-location
e.g. domain.sharefolder/BLABLA/Project
and use Versioning in the time-stamp [File] format in a versioning location
e.g. domain.sharefolder/BLABLA/ProjectVersions
After running a sync, you can then find the latest mirror of C:/BLABLA/Project in
domain.sharefolder/BLABLA/Project
in the identical (sub)folder structure as in C:/BLABLA/Project
and any previous versions in
domain.sharefolder/BLABLA/ProjectVersions
again in the identical (sub)folder structure as in C:/BLABLA/Project and domain.sharefolder/BLABLA/Project