Help  |   Contact Us  |   About Us  |   News and Events
Books, conferences, and other information about... Moving to Linux Switching to OOo Building Linux Apps Using Visual FoxPro
Buy      Download      Your Account      Catalog      Support      Conferences      Resources      Fun

Essential SourceSafe

If you have a question about the technical contents of this book, please contact the author(s). Their email address(es) can usually be found in their bios in the About the Author section at the front of the book or on the author's bio page (click on the author's name on the book's main page.


Thanks to you, readers, for the helpful suggestions, constructive criticisms, and positive feedback on the first edition of Essential SourceSafe. Here are a couple of items that need correction.

Local Web Server SourceSafe configuration (pp 80-81)

If you are configuring InterDev and SourceSafe to work with a configuration where SourceSafe is located on the same machine as the web server, you do not (and should not) have to add the IUSR_ account to SourceSafe. You also do not have to configure the web server for Basic Authentication. These techniques are needed only if the SourceSafe database is on a different machine than the web server.

If you are working on a development web server (always a good idea), usually you will disable anonymous access to the web server. Then, as each developer access the web server, they are authenticated with their own credentials, and checkouts are credited to the correct user account. If you do need to allow anonymous access to the web server, you need to configure Visual InterDev, in the Project | Web Project Web permissions dialogue, typically removing author and admin permission from the Everyone group. So, don't create the ISR_ account as a SourceSafe user unless the SourceSafe database is being accessed remotely by that user and web server.

Thanks to Patrick in Microsoft Product Support for straightening me out on this:

No Help on Lost Passwords (page 219)

When the book was written, Microsoft had a Knowledgebase article suggesting that you contact Product Support Services if you had lost the Administrator's password and needed to recover it. That policy has since been withdrawn, and the "Microsoft's Policy Regarding Missing or Invalid Passwords" standard has been established in its place. In short form, it says that Microsoft will not help you circumvent the security structures they put in place. Fair enough. However, an industrious search of the Internet may provide links to 3rd party vendors who can do this. A careful read of the Troubleshooting chapter may also give you some other ideas on ways to recover from this situation. 'Nuff said.


Due to a cut and paste error, three references to "current" in the ParsePhy.PRG should be "curlist" instead. An updated version has been added to the downloads. Thanks to alert reader Richard Ihmels for catching the error!

What versions of SourceSafe does your book cover?

The book was written for Visual SourceSafe 6.0, and covers all of the features and foibles up through Service Pack 5 for Visual Studio 6.0. The vast majority of the book is applicable as well to the version 6.0c version that shipped with Visual Studio .NET.

Does your book tell me how to work with SourceSafe on the Macintosh or UNIX platforms?

The book is focused on Microsoft's Visual SourceSafe, which runs only on Microsoft's Windows platforms. There are versions of SourceSafe available for the Macintosh ( and UNIX ( and support is available through those vendors. User interface and operations are very similar for the products, and they do have the ability to share data across platforms, but that's beyond the scope of the book.