VSS version 5: Can we fudge it?

[DavidMacLean]

Is it possible to use VSS version 5 with VisualBuild?

I notice the commands seem to work just fine, but Visual Build reports failure (all operations return 100?).

Are there any workarounds? We do not want to upgrade VSS at this time.

Thanks in advance.

Building project step 'SourceSafe'...
"F:\ssafe\win32\SS.EXE" Label $/forum -LTESTLABEL -NL -I-Y -YDavid, -C-
Invalid DOS path: ssafe\srcsafe.ini
Process completed with exit code 100
Step 'SourceSafe' failed
Build ended.

[kevina]

The Invalid DOS path error is probably indicating what is failing.

Here is an msdn reference (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/guides/html/vsgrfers_str_file_badpath.asp for details) documenting that VSS error.

This google search (http://www.google.com/search?hl=en&lr=&q=Invalid+DOS+path) finds several other potentially useful ideas.

[DavidMacLean]

Thank you for your prompt reply.

The main question again is simply this: is it possible to use VSS version 5 with VisualBuild? Are people doing it successfully?

* * *

In the original post: the VSS command executes just fine, VSS performs the requested operation. Done!

It works without error from the command line (even running from the same location as Visual Build, on a different drive from VSS).

But from within VisualBuild it generates this error which stops the build.

In other words, the command is not failing. But VSS and VisualBuild do not appear to be agreeing on the results.

The msdn page talks about an #include line in an INI file (which makes no sense to me): nor does the VSS help file mention #include lines in INI files.

If there are changes required to SRCSAFE.INI to accomodate VisualBuild, does anyone have an example? I cannot imagine how to place an #include directive into an INI file.

Thank you.