Shadow Folders: file date/time to "Modified" - How

M Wickardt · Post by **M Wickardt** » Wed Jul 12, 2006 5:44 am

Hi,

In our environment it's crucial that the Shadow Folder file dates and times are the "Modification" ones, not "Current" or "Check in".

In VSS this was possible, I want to migrate to SourceGear for various reasons, but surprisingly I can't find where to configure this. Is it at all possible?

Thanks for any help,

M Wickardt

System:
Vault client is version 3.1.9.3798
Vault server is version 3.1.9.3798
Server: XP Pro SP2 / SQL Express 2005 / Source

lbauer · Post by **lbauer** » Wed Jul 12, 2006 7:46 am

Currently, the time on files retrieved by the Shadow Folder service is the "get" or current time. I'll log a feature request for the ability to designate "checkin" and "modification" time.

A possible workaround would be to use an automated script with the command line client to get the latest versions instead. You can set file times on gets with the CLC.

M Wickardt · Post by **M Wickardt** » Wed Jul 12, 2006 9:34 am

Thank you for your quick reply.

For the time being, I made a workaround that does a get of the total repository every three seconds, with the character interface. Rather ugly tho.

Is there any way to subscribe to Vault server events? So I can do it only on a check-in, add, or delete event?

Regards, M Wickardt

M Wickardt · Post by **M Wickardt** » Wed Jul 12, 2006 10:24 am

And, another thing: "Branch" sets the Modified date to current! That also gives problems, since our "most recent modified" compiler sees it as a different file, which it's not.

Could you make this optional?

Third timestamp issue: I can't see the Modified file date in the history. With a Get from History, there is an option to use the at that time "Modified" timestamp, and that works. But it's not very practical to have to get the file just to see it's modified date.

Some extra fee is negotiable btw, we're planning to put Vault into production soon. Please send me a PM if that's an option.

Best regards, M Wickardt

Beth · Post by **Beth** » Fri Jul 21, 2006 2:58 pm

Is there any way to subscribe to Vault server events? So I can do it only on a check-in, add, or delete event?

---Emails can be sent for any modification to the database, including rename, share, branch, etc. That feature is set-up in the Admin tool in the Server Options tab under Email Settings. We have a feature request logged to send notifications on checkout.

And, another thing: "Branch" sets the Modified date to current! That also gives problems, since our "most recent modified" compiler sees it as a different file, which it's not. Could you make this optional?

---There is currently a feature request to use the modification time instead. Would you like your vote thrown in for that possibly? If not, I can put in another feature request to make either optional.

Third timestamp issue: I can't see the Modified file date in the history. With a Get from History, there is an option to use the at that time "Modified" timestamp, and that works. But it's not very practical to have to get the file just to see it's modified date.

----We currently have a feature request for that. I will add your vote.

We just released version 3.5 which has some new features you will want to check out. Here's where the release notes are: http://support.sourcegear.com/viewtopic.php?t=6423

Back on the Shadow Folder date, we believe we can get that one in version 3.5.1. It won't be too long before we have that, just not in the next two weeks.

Thanks
Beth

M Wickardt · Post by **M Wickardt** » Sat Jul 22, 2006 2:43 am

Thank you very much for your quick and eleborate answer.

I continue this thread in the Gold forum (I see you have already replied there as well);
http://support.sourcegear.com/viewtopic.php?t=6461

Best Regards, M Wickardt

Post by **jclausius** » Fri Sep 15, 2006 8:40 am

Note - This enhancement is not included in the current Vault 3.5.1 release - which was quickly released to address a problem with Date Time synchronization and a Visual Studio Dialog problem.

The enhancement will be in a more inclusive Vault 3.5 maintenance release which should be out later this year.