0

I have a solution with multiple projects which I don't always want to build at the same time.

So I created several solution configurations like in the following example:

Configuration 1

  • Project A is build
  • Project B is build
  • Project C is not build

Configuration 2

  • Project A is build
  • Project B is not build
  • Project C is build

etc.

It was all working very well until yesterday, when I created a couple of new solution configurations. Since this moment, every time I change configuration, all my project files are checked out although they show no difference with their server version.

Could someone explain this behaviour?

And, more importantly, what can I do to stop it?

Community
  • 1
  • 1
Rodolphe
  • 1,689
  • 1
  • 15
  • 32

1 Answers1

1

it may be hard, but: Stop using SourceSafe, it's well past its support deadline and there is a much better alternative in either and (Express if you need free) both supporting and .

Or any of the non-Microsoft options like and in the cloud or plain or on premise.

The reason why your projects are checked out may simply be because Visual Studio removes the read-only bit, which is something more modern systems no longer need to rely on as they'll actually compare the file contents to determine whether a file needs to be checked out. I've stopped debugging SourceSafe a long, long time ago.

jessehouwing
  • 106,458
  • 22
  • 256
  • 341
  • SourceSafe is such a pain in the neck... I'd really like stop using it. But it's a little bit out of my hands... – Rodolphe Mar 13 '15 at 09:33
  • There is now a VSS to TFS conversion tool from Microsoft. The move is easier than ever before. – jessehouwing Mar 13 '15 at 09:41
  • I'm more than tempted. I need to talk to my colleagues. ;o) – Rodolphe Mar 13 '15 at 09:44
  • I accepted your answer although it was not really what I expected when I came here. But I guess you're right and changing for another source control solution would be for the greater good. – Rodolphe Mar 17 '15 at 13:55