Comments on: All about the .MySCMServerInfo file

By: Understanding File Status in Surround SCM » The Seapine View

Understanding File Status in Surround SCM » The Seapine View — Mon, 23 Aug 2010 14:04:42 +0000

[...] file, which is included in each working directory, to quickly determine file status. I have blogged about this file before. What Does Each Status [...]

By: Visual Studio and Surround SCM » The Seapine View

Visual Studio and Surround SCM » The Seapine View — Tue, 28 Jul 2009 20:31:30 +0000

[...] I wrote a post on the .MySCMServerInfo file, and I mentioned that one of its uses is the IDE integration. In this post, I am going to break [...]

By: Rob Thomas

Rob Thomas — Fri, 10 Jul 2009 20:33:29 +0000

that last post was supposed to say…

and have Surround update the status from unknown to current or modified, etc.

By: Rob Thomas

Rob Thomas — Fri, 10 Jul 2009 20:32:00 +0000

If I already have the files in my working directory, but don’t have the .MySCMServerInfo file, or it’s invalid due to moving the directory structure around, it would be nice to be able just to do a differences, and have Surround update the status from to or , etc.

Unless, there’s another way to update the status w/o doing a GET and possibly over-writing some local changes.

By: Marko Aho

Marko Aho — Tue, 07 Jul 2009 13:13:56 +0000

One thing missing from the .MySCMServerInfo file though is the actual server name the source files are associated. Having multiple servers in the company the server info last connected to is remembered in user’s SCM registry settings (I guess), and if opening solution to IDE with the wrong server in registry, the solution is not found. Now including the actual server name into the .MySCMServerInfo (and using of course) would nicely fix this
Just like using the fully qualified sscm -protocol in the first place: sscm://server:port/Branch/Repository !