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?
it may be hard, but: Stop using SourceSafe, it's well past its support deadline and there is a much better alternative in either visual-studio-online and tfs2013 (Express if you need free) both supporting tfvc and git.
Or any of the non-Microsoft options like github and atlassian-stash in the cloud or plain git or subversion 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.