The information in this article applies to:
- Standard, Professional, and Enterprise Editions of Microsoft
Visual Basic, 16-bit and 32-bit, for Windows, version 4.0
- Microsoft Visual SourceSafe for Windows, version 4.0
SYMPTOMS
The "Add Files to SourceSafe..." command is disabled for projects which are
already under Source Code Control. This is true even if you add a form,
class, or module to your currently controlled project.
STATUS
The "Add Files to SourceSafe..." command is enabled until after the project
is saved (via the Save Project command in the File menu). It is only
enabled if there are files in the project which are not already under
Source Code Control. This behavior is by design.
MORE INFORMATION
Steps to Reproduce Problem
- Start Visual Basic, and open a Visual Basic project which is in
Visual SourceSafe via the "Open New SourceSafe Project" command in the
Add-Ins, SourceSafe menu.
- On the Add-Ins menu, click SourceSafe. Note the "Add Files to
SourceSafe..." command is disabled.
- Check out the .VBP (or .MAK) file for the project via the Tools menu.
- Insert a new form, module, or class to the project via the Insert menu.
- On the Add-Ins menu, click SourceSafe. Note the "Add Files to
SourceSafe..." command is still disabled.
Steps to Demonstrate Behavior
- Follow steps 1-5 from Steps to Reproduce Problem section above.
- On the File menu, click Save Project to save the project.
- When asked to "Save File As", save the new form, class, or module to
your local project working directory. When asked to "Add to
SourceSafe," click the Cancel button to prevent the file from being
automatically added to SourceSafe. At this point, the new form exists
on your local machine, but SourceSafe does not have the file(s).
- On the Add-Ins menu, click SourceSafe. Note the "Add Files to
SourceSafe..." command is now enabled. If you select this command, it
displays the "Add to SourceSafe" dialog box, displaying all forms,
modules, and classes which are not already under Source Code Control.
|