Ten And Six Software
Home of the SSUE utility! What happened to Tom Welch?
ssue is an application written by Tom Welch that helps you checkin and checkout files from SourceSafe simply by using push buttons in the UltraEdit programmers text editor.
For some time it has been impossible to find ssue and I have seen some users have been looking for it. That's why I decided to put up my copy for download here so anyone looking for it can find it.
Tom does not know I'm doing this and I have not been able to contact him, so if you are Tom and you wonder what I'm doing please mail me at sbyholm [ a t ] byholm [ d o t ] com
BE WARNED THAT THIS COPY OF SSUE IS USED AT YOUR OWN RISK AND WITHOUT SUPPORT OR WARRANTY OF ANY KIND! It's provided as a courtesy to old users that have lost their copy.
Download ssue by right clicking and choosing Save Taget As... below:
Use the following tool configuration in UltraEdit to use ssue.exe
Example Command Line:
"C:\Program Files\Microsoft Visual Studio\Common\VSS\Win32\ssue.exe" c:\vsswork checkout "%f" -GWR
Working Directory:
%P
The most recent questions will be shown here, but you are directed to view the FAQ for a full list.
When I run SSUE.EXE it asks me for a Username and Password. Why? [2002.11.07]
This happens when you install Visual Source Safe on your local computer and move the database manually to another computer (most likely a server). When you do this, you need to change your SRCSAFE.INI file to point to the remote database. Instructions for doing this are found in an article titled HOWTO: Move a VSS Database or Project to New Location on Microsoft's support site. This is article #Q176909. See instructions for Senario 3. However, Scenario 1 is the preferred method of moving a database to another computer and SSUE works just fine in that configuration.
From Mike Amundsen
We use a UNC address to access the source files \\share\folder\folder\source. this is also the working directory withing VSS (we all save to the same tree). when running SSUE.exe from Ultra-edit, we kept getting an error that CMD.exe does not support UNC names.
The solution was to add a registry entry that allows UNC names from the command line. this MS KB article outlines the details: http://support.microsoft.com/kb/156276
Once we added that item (and did some tweaking with the working directory and the -PP setting) all works quite well.
This Website is Copyright (C) 2006 Simon Byholm
Ten And Six Software