Discussion:
Getting the MS Visual Source Safe command line option to work
(too old to reply)
championsleeper
2004-03-02 11:43:22 UTC
Permalink
Hi,

Am "desperate" to get the Microsoft Visual Source Safe (vss) command
line interface to work.

Here is my situation:
- running Windows XP Professional ver 2000 service pack 1
- using Microsoft Visual SourceSafe 6.0
- can access projects through VSS Explorer (password not supplied, ini
file I point to contains one entry which points towards the network
folder where the main ini file is and the data itself - file at end.
- on the command line, setup path with location of ss executable,
ssdir with location of srcsafe.ini file with location of LOCAL
srcsafe.ini file and set variable ssuser to appropriate value.

Everytime I attempt to login from the command line I get the response
Username: NAME
Password:

I have never had to give a password on the explorer and do not know
what it is. I have alos tried with ssdir set to the network folder
where the "full" source safe initialization file is located - same
resutlt.

One interesting observation - when I set the values for ssdir, path
and ssuser in the system environemnt variables (as opposed to in a dos
prompt) then it does not work but I do get a prompt for the username
and password when I run the explorer. Under these circumstances, for
some reason, it then points towards a database on the local machine. I
point it towards the network folder and select ok. I can then login
without a password.

I am confused .....
; srcsafe.ini
;
; Three of these variables -- Data_Path, Users_Path, and Users_Txt
-- must
; be in srcsafe.ini. Any other variable here can be overridden in
ss.ini.
; Similarly, any ss.ini variable can be placed in srcsafe.ini to
set a
; system "default," which individual users can still override in
ss.ini.
; The three important paths used by SourceSafe.
Data_Path = data
Temp_Path = temp
; This tells admin where to put personal directories for new
users.
Users_Path = users
; From this, find users.txt; from that, in turn, find ss.ini for a
user.
Users_Txt = users.txt
Use_Network_Name = Yes
Keyword_Masks = *.cpp,*.h,*.pas,*.dpr,*.idl
Multiple_Checkouts = Yes
Shadow =
[Printer Config Files]
Text = text.cfg
PostScript = postscri.cfg
[$/path_removed]
Shadow (PC) =
[$/path_removed]
Shadow (PC) = \\path_removed
Shadow_EOL = N
Shadow_SetTime = Update
[$/path_removed]
Shadow (PC) = \\path_removed
Shadow_EOL = N
Shadow_SetTime = Update
Jim Atwood
2004-05-06 20:08:15 UTC
Permalink
What about setting the SSDIR evironment variable to point to the correct
database?

Jim Atwood
Try working with the local database first. You know the user names, etc. I
see you have Use_Network_Name set to Yes. Make sure that's the same for the
local version while you're working with it. Try specifying the user name
with the -y. Try a different user name, one that you set up with admin. Try
admin.
HTH,
Joe
Post by championsleeper
Hi,
Am "desperate" to get the Microsoft Visual Source Safe (vss) command
line interface to work.
- running Windows XP Professional ver 2000 service pack 1
- using Microsoft Visual SourceSafe 6.0
- can access projects through VSS Explorer (password not supplied, ini
file I point to contains one entry which points towards the network
folder where the main ini file is and the data itself - file at end.
- on the command line, setup path with location of ss executable,
ssdir with location of srcsafe.ini file with location of LOCAL
srcsafe.ini file and set variable ssuser to appropriate value.
Everytime I attempt to login from the command line I get the response
Username: NAME
I have never had to give a password on the explorer and do not know
what it is. I have alos tried with ssdir set to the network folder
where the "full" source safe initialization file is located - same
resutlt.
One interesting observation - when I set the values for ssdir, path
and ssuser in the system environemnt variables (as opposed to in a dos
prompt) then it does not work but I do get a prompt for the username
and password when I run the explorer. Under these circumstances, for
some reason, it then points towards a database on the local machine. I
point it towards the network folder and select ok. I can then login
without a password.
I am confused .....
; srcsafe.ini
;
; Three of these variables -- Data_Path, Users_Path, and Users_Txt
-- must
; be in srcsafe.ini. Any other variable here can be overridden in
ss.ini.
; Similarly, any ss.ini variable can be placed in srcsafe.ini to
set a
; system "default," which individual users can still override in
ss.ini.
; The three important paths used by SourceSafe.
Data_Path = data
Temp_Path = temp
; This tells admin where to put personal directories for new
users.
Users_Path = users
; From this, find users.txt; from that, in turn, find ss.ini for a
user.
Users_Txt = users.txt
Use_Network_Name = Yes
Keyword_Masks = *.cpp,*.h,*.pas,*.dpr,*.idl
Multiple_Checkouts = Yes
Shadow =
[Printer Config Files]
Text = text.cfg
PostScript = postscri.cfg
[$/path_removed]
Shadow (PC) =
[$/path_removed]
Shadow (PC) = \\path_removed
Shadow_EOL = N
Shadow_SetTime = Update
[$/path_removed]
Shadow (PC) = \\path_removed
Shadow_EOL = N
Shadow_SetTime = Update
Continue reading on narkive:
Search results for 'Getting the MS Visual Source Safe command line option to work' (Questions and Answers)
10
replies
Java Vs. C#?
started 2007-01-04 01:45:54 UTC
programming & design
14
replies
Creating a "Why we should switch to Mac" Speech. Help Please?
started 2007-10-26 15:44:14 UTC
desktops
43
replies
Do they have a yahoo Answers where you live?
started 2006-09-14 15:54:56 UTC
polls & surveys
16
replies
Does anyone know what algae,conifers,ferns, moss and angiogram have in common?
started 2007-03-19 03:31:15 UTC
biology
254
replies
Why is my PC so damn slow?
started 2015-08-11 11:59:18 UTC
desktops
Loading...