Treating local read/write files

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

IndyStef - 24 Jul 2006 18:08 GMT

I ran into a problem with VSS2005 that I did not see in VSS6.0.
When I want to recursively get files for a VC6 project, and some of these
files are read/write on my local drive, VSS6 used to give me the option to
leave those files as they are, or replace them with copies from SS. VSS2005
now has 4 options, a) Leave the file, b) Replace the file, c) Check file out
and keep changes, d) Check file out and merge changes. Unfortunately options
a) and d) are disabled (grayed out), so I cannot leave my local files as they
are.
It looks like there must be a way to set this up so I can leave those files
- but how?
Could anybody point out which setting I have to modify?

Thank you,
Stefan

Reply to this Message

Erwan - 25 Jul 2006 11:30 GMT

Hi IndyStef

I just found a thread about this problem, at
http://groups.google.com/group/microsoft.public.vstudio.sourcesafe/browse_frm/th
read/3dd74f26ae23a249/e0cc75b77b93bab4%23e0cc75b77b93bab4
The main point is that, rigth now, the three options you have are :
- either hack the VSS2005 dll of all your machines using VSS2005 so
you'll always have the choice to leave your local file
- or configure VSS2005 so that it will always leave your local file
(without displaying the pop up window)
- or change your SourceSafe configuration to switch from single
checkout to multiple checkout.

It reads in that thread that this feature, which was in VSS6.0 and
before, could be back in a SP since a lot of people seems to run into
that same problem. My problem is that I haven't found any information
about this SP. Does anyone know something about this SP ? A possible
shipping date ?
Regards

Erwan

> I ran into a problem with VSS2005 that I did not see in VSS6.0.
> When I want to recursively get files for a VC6 project, and some of these
[quoted text clipped - 10 lines]
> Thank you,
> Stefan

Reply to this Message

Treating local read/write files

Free Magazines