Essential SourceSafe helps SourceSafe users, software developers, and administrators better use SourceSafe. It covers installation, configuration and operation for SourceSafe in a standalone environment, or in an integrated environment with Microsoft Visual Studio 6.0, Microsoft Office 2000 Separate chapters cover installation, operation, configuration, and instructions for integration with individual products. The remainder of this document is an enhanced table of contents, with the introductory paragraphs from each chapter. Chapter 1: Visual SourceSafe Server and Client Install, Basic Administration This chapter covers the process of installing the software, a good first step. It covers where you should install the components, and what gets installed. Once SourceSafe is installed, you use the Visual SourceSafe Administrator, covered in depth later in the book, to set up user logins. At the completion of this chapter, you’ll be all set up for the next chapter, where you get to start working with SourceSafe. Before you can do much of anything with Visual SourceSafe, you need to install it. That’s what’s covered first in this chapter. After that, there’s a section documenting which files landed where. The final portion of this chapter walks you through the process of setting up your first user account. In the next chapter, you get to actually create your first SourceSafe project. How many installs do I do? - Installing Visual SourceSafe as a stand-alone product - Installing VSS as part of the Visual Studio install - Installing VSS as part of a Microsoft Office Developer install What files get installed where? Update SourceSafe with service packs VSS is installed—now what? Creating user accounts Configuring the database for integration Summary Chapter 2: Terminology and Philosophy – using VSS as a stand-alone tool So far, Chapter 1, “Visual SourceSafe Installation,” helped you install Visual SourceSafe and configure it. This chapter looks at what SourceSafe does for you—how it stores information, how it presents your projects, and how you can check files in and out and track changes. This chapter explains what SourceSafe is doing with operations named checkout, check in, difference, branch, pin and merge. In this chapter, you get to run the Visual SourceSafe client, also called the Explorer, create a sample project and source code, and exercise the functions made available through the VSS Explorer interface. The last portion of this chapter reviews each of the dialogs presented by SourceSafe, pointing out important features and hazards. The primary purpose of SourceSafe is to store, retrieve and track the history of multiple versions of computer files. These files could be source code for a development project, Word documents for a marketing campaign, or CAD drawings for a building renovation. The contents are generally not important to SourceSafe (although later on, the difference between binary and text files is discussed); SourceSafe’s job is to track the documents and their changes over time. This chapter discusses the interface of the SourceSafe Explorer and, in the process of doing that, all of the functionality available within the product. The theory: Learning to climb the tree Tutorial: Climbing the tree The reality: Swinging through the branches Multiple checkouts and the Dreaded Visual Merge form Is the hassle worth it? The Explorer interface Toolbar Menu Project tree view File pane Results pane Status bar Drag and drop Reports Dialog by dialog The File menu The Edit menu The View menu The SourceSafe menu The Tools menu The Web menu Chapter 3: Configuring for applications Once you have your applications and Visual SourceSafe installed, the next step is to let your applications know that VSS is available and that the application should use it as its source code control provider. Each application is a little different in how you perform that step and in the options you have to configure. This chapter serves as a guide to administrators and users in setting up their applications for SourceSafe integration. Chapter 1, “Visual SourceSafe Installation,” covered the basics of installing and configuring Visual SourceSafe. Chapter 2, “SourceSafe in Theory and Practice,” reviewed the use of SourceSafe as a stand-alone tool, reviewing the basic design concepts of source code control as implemented in SourceSafe, and then walking through the interface of the stand-alone product. In this chapter, you will see how SourceSafe can also be integrated into other products, becoming part of their interface. Each application needs to be configured, and each has options that affect how the product works. The SCCAPI mechanism Standardize on one configuration for the team Configuring Visual FoxPro Configuring Visual Basic SourceSafe common Advanced options Configuring InterDev and Visual J++ Configuring Visual InterDev for Web projects Configuring C++ Configuring Microsoft Office Configuring FrontPage Configuring InterDev and SQL Server for data projects Summary Chapter 4: Visual Studio Interfaces Now that the product is installed and configured, and you’ve seen what functionality is available through the VSS Explorer interface, this chapter looks at the capabilities exposed in each of the Visual Studio applications. This chapter documents the day-to-day operations that you will perform using your Visual Studio development environments and integrated source code control using Visual SourceSafe. Should you use integration? How it works: The big picture - Creating a new project - Joining an existing project - Maintaining existing code - Adding new code to a project - Bringing an existing project into source code control The devil’s in the details - Are metadata and process information data, or are they code? - What about development and test data? - Should my add-on tools, build tools and setup tools be in SourceSafe, too? - How to handle projects with remote developers - What to do when the project gets mangled? Visual FoxPro - SCCTEXT.PRG - Routine source control operations with VFP - Problems with Visual FoxPro integration Visual Basic - How it works - Problems with VB integration Visual C++ - How it works - Problems with VC++ integration Summary Chapter 5: Visual InterDev interface and SQL Server Using Visual InterDev with integrated source code control is similar in many respects to the interfaces presented in the Visual Studio tools, but it’s significantly different, too. In this chapter, we’ll look at how accessing SQL Server stored procedures or Web-based pages via IIS works differently than the direct access to source code in the Visual Studio integration. The InterDev interface Visual InterDev and Internet Information Server Visual InterDev and SQL Server Summary Chapter 6: Working with Microsoft Office The Microsoft Office Developer Edition (yes, MODE) supplies the add-ins to allow Access 2000 and the Office VBA Editor to use SourceSafe as their source code control provider. MODE also includes an updated version of SourceSafe itself. Chapter 1, “Visual SourceSafe Installation,” discusses installing Visual SourceSafe as a stand-alone product, as part of the Visual Studio installation, or as part of the MODE installation. Chapter 3, “Configuring Applications,” covers the basics of configuring Access, Visual Studio, Microsoft Office and Visual Basic. In this chapter, I show how SourceSafe integration works within the Office tools. Microsoft Office Developer Edition VBA/VB interface Access What’s going on under the hood Issues with Office and SourceSafe Summary Chapter 7: Maintaining This chapter covers the work an administrator will do to maintain the SourceSafe installation: configuring the Administrator tool, performing backups, testing the structure of the Visual SourceSafe database, maintaining the security system,