#2
|
|||
|
|||
I haven't encountered that, but it does appear to be a SourceSafe issue (the SourceSafe action invokes the VSS command-line executable to actually perform a SourceSafe operation). You can check the 'Log command-line...' option on the Advanced tab, rebuild and include the ss.exe command-line when contacting MS support.
|
|
|