We have a VB project that is being developed by several users. The project is under MS Visual SourceSafe version control.
The problem is that the .vbp file must be checked out to add a form, module, etc., but only one person can check the file out at a time. So when I have it checked out to add a form, no one else can be adding a form or module. In addition, once I check in the new form and the new .vbp file, the other developers have no idea that those files have been checked in unless they do a get latest version of the project file.
Now, maybe the VSS model we are using is wrong. The basics are that the working files are in a directory \\server\UserX\app. VSS puts these in as read-only for all files except those which have been checked out by UserX.
In other applications you can use a path statement to get around this problem. If you use a Shadow folder in VSS, the checked-in files are written to \\server\dev\app. UserX has his checke out or new files in \\server\UserX\app and so you set up a PATH = \\server\UserX\app;\\server\dev\app. Thus, any checked-out files are found by the app before the checked-in files.
Is there any way to do this in VB? Or is there another way to solve this problem?