File dates problem using automation
Doug Hutcheson
.
I posted this question about a week ago and had no replies. Posting
again in the hope that someone has an idea for me ...
We use VSS 6 in a key project involving Windows, Unix, Tuxedo, Java,
Jolt and HTML elements. The repository is on an NT server and we talk to
the Unix boxes via Samba.
I am lucky (?) enough to be locked in as migration manager, using the
facilities of VSS to help move product from development, through various
test layers and finally into production.
When I print reports from VSS (Tools / Files Reports), the dates shown
are those displayed on the VSS browser window - in other words, the file
datestamps. These reports are of very limited use, as they do not
include the file version or the VSS action history date, which means
they cannot be cross-checked against the VSS database once the files
they list have been changed.
When I try print more meaningful reports via automation, using the
VSSVersion date property, the dates reported are those displayed in the
VSS History window - in other words, the VSS action datestamps. I cannot
cross-reference my reports to the VSS Files reports because the
last-edited date does not match the VSS action date.
These dates can clearly vary - a file can be last edited on 1 October at
10:00am but checked back into VSS on 1 October at 4:00pm. The VSS Files
Report will show "1 October 10:00am", but the report through automation
will show "1 October 4:00pm".
In order to prepare fully cross-referenced baseline listings from VSS, I
therefore need to extract the file datestamp and the action datestamp
separately. Is there a VSSItem or VSSVersion property I am missing,
which will allow me to extract the file date stamp - the date displayed
in the VSS browser window? I am baffled.
"8-\
Kind regards,
Doug Hutcheson
Brisbane, Australia