RE: vault.exe history command

Right.  If I can pass in any DateTime that may or may not have a time
element to it and the clc can deal with it, then great.  I was just
worried that it would only be looking at mm/dd/yyyy as its filter and
would be ignoring time completely.

Thanks,
Ryan

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of jeff
clausius
Sent: Tuesday, April 20, 2004 10:29 AM
To: [email protected]
Subject: RE: [vault-list] vault.exe history command

after dwelling on this, we'll probably just let the .net framework
handle the parsing (in which you do not specify hour/min/sec if you do
not wish to).  in this way, the clc will be able to use people's
cultural settings to determine how the date/time string should be
converted.

jeff

*********** REPLY SEPARATOR  ***********

On 4/20/2004 at 9:56 AM Ryan Duffield wrote:

>Do the BEGINDATE and ENDDATE options only support year/month/day, or do

>they also support hours/minutes/seconds?
>
>Thanks,
>Ryan
>
>-----Original Message-----
>From: [email protected]
>[mailto:[email protected]] On Behalf Of jeff=20
>clausius
>Sent: Tuesday, April 20, 2004 9:35 AM
>To: Ryan Duffield
>Cc: [email protected]
>Subject: Re: [vault-list] vault.exe history command
>
>i see the following supported options:
>
>-ROWLIMIT INT_NUMBER
>-BEGINDATE yyyy-mm-dd
>-ENDDATE yyyy-mm-dd
>
>it appears the clc supports the options, but does not use that info in=20
>the request for history.  i'll log this for fixing.
>
>thanks,
>jeff
>sourcegear
>
>
>*********** REPLY SEPARATOR  ***********
>
>On 4/20/2004 at 8:53 AM Ryan Duffield wrote:
>
>>Hi,
>>
>>I have just finished my CruiseControl.NET classes for Vault, which=20
>>simply wrap the command line client.  I noticed that there are no=20
>>options to limit the results returned by the history command by date.
>>For example, it would be nice to be able to specify "history fromDate=20
>>toDate $".  I don't know if something like that is supported by the=20
>>client API, but if it is, that would be a nice feature to expose in=20
>>future command line client versions.
>>
>>For now I am simply loading the response into an XmlDocument and=20
>>filtering by the date attribute on the items.
>>
>>Thanks,
>>Ryan
>>_______________________________________________
>>vault-list mailing list
>>[email protected]
>>http://lists.sourcegear.com/cgi-bin/mailman/listinfo/vault-list
>
>
>
>_______________________________________________
>vault-list mailing list
>[email protected]
>http://lists.sourcegear.com/cgi-bin/mailman/listinfo/vault-list
>
>_______________________________________________
>vault-list mailing list
>[email protected]
>http://lists.sourcegear.com/cgi-bin/mailman/listinfo/vault-list



_______________________________________________
vault-list mailing list
[email protected]
http://lists.sourcegear.com/cgi-bin/mailman/listinfo/vault-list