If the share is named midas$ (a hidden share), why should it be
renamed?
I had a similar problem. The directory was not hidden though. In my
case, the $$ threw an IOException.
In my case, midas$ is a hidden share and using $$ caused no
problems, (thanks for that Nico). My original
To: Ant Users List
Subject: Re: Problem with Visual SourceSafe task
- Original Message -
From: Shawn McManus [EMAIL PROTECTED]
To: Ant Users List [EMAIL PROTECTED]
Sent: Tuesday, November 27, 2001 10:12 PM
Subject: RE: Problem with Visual SourceSafe task
I don't think that your
- Original Message -
From: Shawn McManus [EMAIL PROTECTED]
To: Ant Users List [EMAIL PROTECTED]
Sent: Wednesday, November 28, 2001 10:19 PM
Subject: RE: Problem with Visual SourceSafe task
If the share is named midas$ (a hidden share), why should it be
renamed?
I had a similar
I've used this VSS label task invocation successfully:
vsslabel
vsspath=/Development Code/myProject/server
ssdir=${vssRoot}\win32
label=${buildName}
serverPath=${vssRoot}
/
...where vssRoot is the UNC path that points to the directory containing the
appropriate
I don't think that your serverpath should end with $. Rather, it
should read,
serverPath=\\private1\midas
Shawn
-Original Message-
From: Ron Coutts [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, November 27, 2001 3:02 PM
To: 'Ant Users List' (E-mail)
Subject: Problem with Visual SourceSafe
- Original Message -
From: Shawn McManus [EMAIL PROTECTED]
To: Ant Users List [EMAIL PROTECTED]
Sent: Tuesday, November 27, 2001 10:12 PM
Subject: RE: Problem with Visual SourceSafe task
I don't think that your serverpath should end with $. Rather, it
should read,
serverPath
- Original Message -
From: Ron Coutts [EMAIL PROTECTED]
To: 'Ant Users List' (E-mail) [EMAIL PROTECTED]
Sent: Tuesday, November 27, 2001 10:02 PM
Subject: Problem with Visual SourceSafe task
Also, there seems to be an inconsistency between the VSS task, and VSS
itself. In my working
