Hi

We use MS Visual Source Safe and perform SSC operations from PB as part of our automatic complier routine. We use the SSC command line options to invoke the operations we need. You could try the same.

just for info the registry (under Wow6432Node) contains the following under InstalledSCCProviders:

The Chinese characters imply some corruption or Unicode issue, I know it's a stupid question, but can you perform the operations that you are trying to do manually on the same machine using the SSC Gui?

What do you have in the registry under that key?

Failing that, sample code that you are using would help.

Regards

David

PBSearch has a Global Search and Replace that will automatcially perform a checkout of all changed objects.

http://www.topwizprogramming.com/pbsearch.html

Hi roland,

i've been testing your Tool PBSearch and it's great but i need to make a lot of changes and i dont want to do it manually.

I've made a little modification in Global Replace from PBTools (basically i add a lot rows of texts for replacing from a file configurated in a specified way). It works fine, changes are made in objects. Problem is project is under SCC and im not able to connect to SCC, and i dont know if i could connect to SCC someday how to set objects checkout and change code. PBORCA_CompileEntryImport change code and set object to checkout?

Ideal for me would be a mix between my modified PBTools (managing all changes to do) and PBSearch (managing changes with SCC):

Thanks in advance

Thanks for your reply.

From command line i can connect.

But i need Search and replace funcionality.

You could use the SSC command line to get the objects you want to change below is an extract from the help file:

Using the VSS Command Line

See Also

You can use the VSS command line to run batch files and macros. In addition, you can use the command line to perform all VSS Explorer commands.

Carrying Out Commands on the Command Line

You can start a command shell from Windows 95 or Windows NT and type VSS commands from there. To do this, the VSS folder must be on your path (set with the PATH environment variable).

You can also use the Run command on the Windows Start menu to run a specific command. For example, you can type ss Get *.* to get all files in the current project.

Command-Line Syntax

Command-line commands have the following general syntax:

ss command [one or more items] [one or more options]

What an item is depends on the command. For instance, for the Get command, an item is a VSS file or project; for the Add command, an item is an operating system file.

In almost all cases where you can specify an item to act on, you can specify more than one item. For instance, any of the following are valid ways of executing the Get command:

ss Get HELLO.C
ss Get HELLO.C HELLO.H TEST.H makefile
ss Get *.C *.H makefile linkfile
ss Get *.*

The command line is case-insensitive, that is, the command ss Get HELLO.C can also be typed as ss get Hello.c.

Note   You do not have to type an entire command name for the VSS command line to recognize it; you need only type enough of the name for VSS to be able to distinguish it from every other command. In most cases, typing the first two or three characters is sufficient.

Command-Line Options

In addition to the command and the items, you can specify options, or parameters. Options are preceded by a hyphen and modify the command. A few options are specific to a command, and are described in that command's command-line Help topic. There is also a set of general options applicable to many commands. They are described in the following table.

Use quotation marks around the entire parameter whenever an item or option contains the space character as part of a string of text. For example, use "-CThis is the comment" rather than -C"This is the comment". Otherwise, VSS treats the space as a separator between different parameters, and the command either fails or yields unexpected results.

Finally i've bought PbOrcapi from Roland.

Thanks in advance.