Thank you all for replies..it finally worked. Now..is there any chance I can
display only the files it gets or replaces..and not the whole list? Its not
a big deal, but it would be nice to either display just the new/replaced
files, or not display anything at all. Is there an option for that?
Thanks again.
> -----Original Message-----
> From: Liu, Kenneth Albert (Kenneth)** CTR **
> [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, February 06, 2001 1:02 PM
> To: [EMAIL PROTECTED]
> Subject: RE: VSSGET problems..
>
>
> We have the VSS directory on the machine where our VSS
> repository is located
> shared
> under NT. So in our build scripts we access the ss.exe
> located on that
> machine
> instead of the one on the local box.
>
> You can run Ant in verbose mode (-verbose) to see exactly
> what command line
> you are using.
>
> Also make sure you are using the newest version of Ant, there
> were some
> patches
> applied to VSSGET since Ant version 1.2. There is also a
> VSSLABEL task but
> I don't think it's documented in the main Ant documentation.
>
> Ken
>
> > -----Original Message-----
> > From: Duffey, Kevin [mailto:[EMAIL PROTECTED]]
> > Sent: Tuesday, February 06, 2001 3:42 PM
> > To: '[EMAIL PROTECTED]'
> > Subject: VSSGET problems..
> >
> >
> > Hi all,
> >
> > I wrote a while back on this problem and still seem to be
> > having it. I am
> > trying to use the <vssget> command, and the syntax is
> > correct. However, when
> > I run the script, I see the output box (DOS window that
> pops up) show
> > VSSGET: username:kduffey and then it just hangs there.
> > Nothing shows up.
> > It never returns. First..is a list of files supposed to be
> > displayed there
> > if it gets any new files? Second, I set the SSUSER
> > environment variable,
> > restarted my machine, etc..and it still keeps asing me for
> > the username. If
> > I go to CMD (win2K) and I type in ss at the prompt, it also
> > asks me for the
> > login name. When I enter my valid login name and my password,
> > it continues
> > to tell me user does not exist. So, my thought here is that
> > for whatever
> > reason, its not hitting the right VSS database, which is
> > located out on the
> > network. We have client VSS installed for each workstation.
> > Any ideas on why
> > this may be a problem and how to circumvent it?
> >
> > Thanks.
> >
>
