I have a configuration file in "ProjectA" that is updated on a regular basis, and is used by an application in "ProjectB". So within "ProjectB" I've done a "Share To $/.../ProjectA/the_configuration_file.conf" in the (possibly vain) hope that the developers on "ProjectB" would get a fresh copy of the configuration file whenever they launched Visual Studio 2008 and did a "Get Latest" from the "Solutions Explorer" panel.

But, unforunately, the file doesn't get updated. Works like a charm if you do a "Get Latest" from the Visual SourceSafe Explorer, but doesn't work at all with a "Get Latest" from Visual Studio 2008.

So is this a known issue? I've been trying to track down a patch, or a fix, or anything that will help me get this working right. Feel free to slap me alongside the head if I'm missing something obvious, here...

Thanks!

Jerry H.

Hi Jerry,

Hi Jerry,

Please try installing the SourceSafe CTP to see if helps:
http://blogs.msdn.com/richardb/archive/2007/11/19/vs-2008-users-remember-to-download-the-sourcesafe-ctp.aspx

Hi Jerry,

Ah-HA! Took me a while to figure out all of the combinations and permutations, but your recommendations seem to be working! Complete destructions for those facing the same problem.

-- Download and install both (?) of the updates for Visual Source Safe 2005:

http://support.microsoft.com/default.aspx/kb/943847
http://support.microsoft.com/default.aspx/kb/939808

-- Follow Catherine's instructions for getting the file share working; to wit:

�Share the file to ProjectB in SourceSafe Explorer.
�Get the file to the local folder of ProjectB.
�Open ProjectB in Visual Studio and add the file by using Add->Existing Item.
�Check in the file.

Note that changes to the file have to be made from "ProjectA" (the permutation), but that's fine by me!

Thanks again!

Jerry H.

Glad to hear that it is working for you.