>>Open your project and do the Add Project to Source Control from the Project menu. This will add all your files in the project to SourceSafe. Once the project is under source safe control, you'll need to enable multiple checkouts (in VSS). Then your other developers can "check out" the project by using the File/Join Source Control Project.
>
>Here problems ocurr. When adding many of the files I get the message: "File <
>\xx.bmp could not be mapped to the SourceSafe project $/Esc03". So I am stuck here, which is roughly the same point as I was stuck at before I asked for help, except now I know a little more...
>
>Do you have an idea of what may be the problem with that?
SourceSafe doesn't like things that live in folders that are not below your main folder (project) of your app. IE, folders on a different drive, folders at your level or above in the hierarchy. You're pretty much stuck with essentially duplicating a lot of info (at least in SourceSafe) so that the folder structure (SourceSafe projects) all occur within one hierarchy. The things can exist in the different places, you just have to be sure to set the working folders separately for each of those in SourceSafe. Kind of a bother and not at all intuitive, IMO. I know the above description is not very clear, but it's kind of hard to explain. Just wait to you try to do branching and merging in SourceSafe for "hard to explain". < bg >
>>I may be a bit light on the details as I haven't set up a new project in awhile. I'd also suggest you get Ted Roche's book Essential SourceSafe from www.hentzenwerke.com. Lot's more details there, too. There's also quite a few MSDN articles you can search for online on "how to" setup SourceSafe.
>
>I think a book may be overkill at this point but who knows. Thanks for the help.
Ted's book, explains some of the concepts of SourceSafe a lot clearer than it's help files do, that's for sure. The KB articles are actually quite helpful, too.
