RE: Problem with Visual SourceSafe task

2001-11-29 Thread Ron Coutts


> > 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 problem, (VSS complaining
that the SSDIR environment variable had not been set), has mysteriously
dissapeared, even without the escape "$".  I discovered this the day
after posting my original message when I was going to try Nico's
suggestion of adding another "$".  The only thing that had changed is
that I had rebooted my machine, so I'm still at a loss to explain why I
had the problem in the first place.  Anyway, I just wanted to relay that
to the thread.

Ron
  

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 




Re: Problem with Visual SourceSafe task

2001-11-28 Thread Nico Seessle

- 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 problem.  The directory was not hidden though.  In my
> case, the "$$" threw an IOException.
>

A single $-sign is used by Ant to detect a property in the buildfile. If
there is no property found the $-sign is simply removed.

A double $-sign is used to escape this behaviour and simply use a real
$-sign somewhere in your buildfile. It is reeplaced with a single $-sign.

There is *no* magic with this, and putting $$ somewhere does not help you
with anything, if there is no need for a $-sign.

If you still have trouble with this IOException, it would be nice, if you
could send some more info.

Nico



--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>




RE: Problem with Visual SourceSafe task

2001-11-28 Thread Shawn McManus

> 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.

-Original Message-
From: Nico Seessle [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 28, 2001 1:46 AM
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 serverpath should end with "$".  Rather, it
> should read,
> serverPath="\\private1\midas"

If the share is named "midas$" (a hidden share), why should it be
renamed?

He should try serverPath="\\private1\midas$$" (escaping the dollar-sign
to
prevent Ant from trying to replace it as a property)

Nico




--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>




Re: Problem with Visual SourceSafe task

2001-11-27 Thread Nico Seessle

- 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 scripts, I set 'SSDIR=\\private1\midas$', i.e. to
> the directory where the srcsafe.ini file is located.  However in the VSS
> task, the ssdir attribute is supposed to refer to the directory where
> the ss.exe file is located.  Is this correct, or a documentation typo?

This is correct (unfortunately).

ssdir was there first and worked well for people who had set up a single VSS
database with registry-entries pointing to it. Then came the need to
dynamically switch databases and we needed another attribute to do this (to
not introduce incompabilitites with older buildfiles).

Maybe something that should be changed in Ant 2.0 too.

Nico



--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>




Re: Problem with Visual SourceSafe task

2001-11-27 Thread Nico Seessle

- 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="\\private1\midas"

If the share is named "midas$" (a hidden share), why should it be renamed?

He should try serverPath="\\private1\midas$$" (escaping the dollar-sign to
prevent Ant from trying to replace it as a property)

Nico




--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>




RE: Problem with Visual SourceSafe task

2001-11-27 Thread Shawn McManus

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 task


The VSS task does not seem to work properly.  I'm getting the error 'No
VSS database (srcsafe.ini) found.  Use the SSDIR environment variable or
run netsetup'.  Currently I'm using the VSS command line interface from
Perl scripts to do gets, and in those scripts the SSDIR environment
variable must be set.  For some reason, the VSS task is not setting this
environment variable.  What am I doing wrong?

Also, there seems to be an inconsistency between the VSS task, and VSS
itself.  In my working scripts, I set 'SSDIR=\\private1\midas$', i.e. to
the directory where the srcsafe.ini file is located.  However in the VSS
task, the ssdir attribute is supposed to refer to the directory where
the ss.exe file is located.  Is this correct, or a documentation typo?

Thanks in advance for any help provided.

Ron


P.S. 
Here's the build file I'm using:








And here's the Ant output:

Buildfile: build2.xml

get:
   [vssget] No VSS database (srcsafe.ini) found.  Use the SSDIR
environment variable or run netsetup.

BUILD FAILED

D:\midasroot\Developers\RonC\AntTests\VssTest\build2.xml:11: Failed
executing: "C:\Program Files\Microsoft Visual Studio\Common\VSS\win32\ss
" Get $/MidasWksp -GLD:\delme -I- -YAutoUser,adrs

Total time: 1 second



--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>




RE: Problem with Visual SourceSafe task

2001-11-27 Thread Harvey, John

I've used this VSS label task invocation successfully:



...where vssRoot is the UNC path that points to the directory containing the
appropriate srcsafe.ini (no slash at the end).  I found it very important to
supply the ssdir directory to allow ant to know where ss.exe is located.

-Original Message-
From: Ron Coutts [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, November 27, 2001 4:02 PM
To: 'Ant Users List' (E-mail)
Subject: Problem with Visual SourceSafe task


The VSS task does not seem to work properly.  I'm getting the error 'No
VSS database (srcsafe.ini) found.  Use the SSDIR environment variable or
run netsetup'.  Currently I'm using the VSS command line interface from
Perl scripts to do gets, and in those scripts the SSDIR environment
variable must be set.  For some reason, the VSS task is not setting this
environment variable.  What am I doing wrong?

Also, there seems to be an inconsistency between the VSS task, and VSS
itself.  In my working scripts, I set 'SSDIR=\\private1\midas$', i.e. to
the directory where the srcsafe.ini file is located.  However in the VSS
task, the ssdir attribute is supposed to refer to the directory where
the ss.exe file is located.  Is this correct, or a documentation typo?

Thanks in advance for any help provided.

Ron


P.S. 
Here's the build file I'm using:








And here's the Ant output:

Buildfile: build2.xml

get:
   [vssget] No VSS database (srcsafe.ini) found.  Use the SSDIR
environment variable or run netsetup.

BUILD FAILED

D:\midasroot\Developers\RonC\AntTests\VssTest\build2.xml:11: Failed
executing: "C:\Program Files\Microsoft Visual Studio\Common\VSS\win32\ss
" Get $/MidasWksp -GLD:\delme -I- -YAutoUser,adrs

Total time: 1 second



--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>



--
This message is intended only for the personal and confidential use of the designated 
recipient(s) named above.  If you are not the intended recipient of this message you 
are hereby notified that any review, dissemination, distribution or copying of this 
message is strictly prohibited.  This communication is for information purposes only 
and should not be regarded as an offer to sell or as a solicitation of an offer to buy 
any financial product, an official confirmation of any transaction, or as an official 
statement of Lehman Brothers.  Email transmission cannot be guaranteed to be secure or 
error-free.  Therefore, we do not represent that this information is complete or 
accurate and it should not be relied upon as such.  All information is subject to 
change without notice.



--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>




Problem with Visual SourceSafe task

2001-11-27 Thread Ron Coutts

The VSS task does not seem to work properly.  I'm getting the error 'No
VSS database (srcsafe.ini) found.  Use the SSDIR environment variable or
run netsetup'.  Currently I'm using the VSS command line interface from
Perl scripts to do gets, and in those scripts the SSDIR environment
variable must be set.  For some reason, the VSS task is not setting this
environment variable.  What am I doing wrong?

Also, there seems to be an inconsistency between the VSS task, and VSS
itself.  In my working scripts, I set 'SSDIR=\\private1\midas$', i.e. to
the directory where the srcsafe.ini file is located.  However in the VSS
task, the ssdir attribute is supposed to refer to the directory where
the ss.exe file is located.  Is this correct, or a documentation typo?

Thanks in advance for any help provided.

Ron


P.S. 
Here's the build file I'm using:








And here's the Ant output:

Buildfile: build2.xml

get:
   [vssget] No VSS database (srcsafe.ini) found.  Use the SSDIR
environment variable or run netsetup.

BUILD FAILED

D:\midasroot\Developers\RonC\AntTests\VssTest\build2.xml:11: Failed
executing: "C:\Program Files\Microsoft Visual Studio\Common\VSS\win32\ss
" Get $/MidasWksp -GLD:\delme -I- -YAutoUser,adrs

Total time: 1 second



--
To unsubscribe, e-mail:   
For additional commands, e-mail: