working folders, spaces in paths

[inthehouse]

Does source offsite support spaces in the database paths?

I've set up two test databases on the server, one with spaces in
the path and one without. The server cannot open the path with
spaces. How can I fix this?

Also, Where are the working folders stored on the SOS client/server?
I usually work by setting the root path and letting all child projects
inherit from the root. I've just tried to check out an entire project
and got the checkout "cross threaded" by having explicit
working folders set in the child projects. This has happened
because visual studio sets the working folder when integration
is enabled. I usually fix this when in the office by editing ss.ini
and deleting the incorrect paths.
Setting working folders in the client is such a pain, as it is
difficult to check that all children have no explicit path set.

Regards,

inthehouse

[lbauer]

Yes, SOS should be able to handle spaces in the database path. A common path to a scrsafe.ini file is C:\Program Files\Microsoft Visual Studio\Common\VSS, for instance.

It's possible SOS can't open one of the databases because the SOS Server service doesn't have access to the machine\drive\directory where the database resides. Check the properties of the SOS Server Service in Control Panel->Admin Tools->Services and use a domain account instead of the Local System account for the SOS Server service.

Working folder information is stored in the SOS Client cache files, called databaseX.sos:

These are in the SOS Client "Servers" folder, which can be found in:
-- SOS 3.x -- the SourceOffSite folder on the SOS Client machine,
-- SOS 4.x -- C:\Documents and Settings\<username>\Application Data\SourceGear\SOS on the SOS Client machine.

We generally recommend using the Visual Studio or VS.NET defaults for working folders, as the IDE expects a particular working folder structure.