Microsoft KB Archive/174650: Difference between revisions
(importing KB archive) |
m (Text replacement - """ to """) |
||
| Line 61: | Line 61: | ||
== RESOLUTION == | == RESOLUTION == | ||
Disable the option | Disable the option "Get latest checked-in versions of files when opening a VB project" as follows:<br /> | ||
<br /> | <br /> | ||
# On the Tools menu, select SourceSafe and then select Options. | # On the Tools menu, select SourceSafe and then select Options. | ||
# Change the setting to | # Change the setting to "No" or "Ask". | ||
This change may have wider implications for the functionality of the Visual SourceSafe integration, which should be taken into account. It is only mentioned here as a resolution to the specific problem described in this article.<br /> | This change may have wider implications for the functionality of the Visual SourceSafe integration, which should be taken into account. It is only mentioned here as a resolution to the specific problem described in this article.<br /> | ||
| Line 73: | Line 73: | ||
All .vbp's that do not show as being source controlled must be removed from and then added back to the .vbg. Visual SourceSafe integration then works with all the .vbp's.<br /> | All .vbp's that do not show as being source controlled must be removed from and then added back to the .vbg. Visual SourceSafe integration then works with all the .vbp's.<br /> | ||
<br /> | <br /> | ||
'''NOTE''': In either case, to be sure you have the most recent copies of the project files in your working folder, you must do | '''NOTE''': In either case, to be sure you have the most recent copies of the project files in your working folder, you must do "Get Latest Version..." for each project in the group. | ||
</div> | </div> | ||
| Line 82: | Line 82: | ||
=== Steps to Reproduce Behavior === | === Steps to Reproduce Behavior === | ||
# Create a new Visual Basic project (.vbp), save it as | # Create a new Visual Basic project (.vbp), save it as "Project1" and add it to Visual SourceSafe through the Visual Basic menus (that is, One the Tools menu, select Visual SourceSafe and then select Add Project to SourceSafe.) | ||
# From the File menu, choose Add Project and then add a new project. This will create a Project Group (.vbg) file. | # From the File menu, choose Add Project and then add a new project. This will create a Project Group (.vbg) file. | ||
# Save the new .vbp as | # Save the new .vbp as "Project2" and add it to Visual SourceSafe as in step 1. | ||
# Exit Visual Basic, and save the .vbg as | # Exit Visual Basic, and save the .vbg as "Group1" file when prompted. | ||
# Restart Visual Basic and open Group1.vbg - note that the Project Explorer's glyphs indicate that one .vbp is source controlled, while the other is not. The project that is not source controlled normally has a glyph indicating that it is read-only. | # Restart Visual Basic and open Group1.vbg - note that the Project Explorer's glyphs indicate that one .vbp is source controlled, while the other is not. The project that is not source controlled normally has a glyph indicating that it is read-only. | ||
Latest revision as of 11:07, 21 July 2020
Article ID: 174650
Article Last Modified on 5/1/2001
APPLIES TO
- Microsoft Visual SourceSafe 5.0 Standard Edition
- Microsoft Visual SourceSafe 6.0 Standard Edition
- Microsoft Visual Basic 5.0 Control Creation Edition
- Microsoft Visual Basic 5.0 Enterprise Edition
This article was previously published under Q174650
SYMPTOMS
When you open a Visual Basic group file (.vbg) that contains multiple, source-code controlled Visual Basic Projects (.vbp), only one .vbp appears to be under Visual SourceSafe control.
CAUSE
You have enabled the option to get the latest version of all the files when opening the project, but Visual Basic is not able to perform the get latest version on multiple projects simultaneously.
RESOLUTION
Disable the option "Get latest checked-in versions of files when opening a VB project" as follows:
- On the Tools menu, select SourceSafe and then select Options.
- Change the setting to "No" or "Ask".
This change may have wider implications for the functionality of the Visual SourceSafe integration, which should be taken into account. It is only mentioned here as a resolution to the specific problem described in this article.
-or-
All .vbp's that do not show as being source controlled must be removed from and then added back to the .vbg. Visual SourceSafe integration then works with all the .vbp's.
NOTE: In either case, to be sure you have the most recent copies of the project files in your working folder, you must do "Get Latest Version..." for each project in the group.
MORE INFORMATION
Steps to Reproduce Behavior
- Create a new Visual Basic project (.vbp), save it as "Project1" and add it to Visual SourceSafe through the Visual Basic menus (that is, One the Tools menu, select Visual SourceSafe and then select Add Project to SourceSafe.)
- From the File menu, choose Add Project and then add a new project. This will create a Project Group (.vbg) file.
- Save the new .vbp as "Project2" and add it to Visual SourceSafe as in step 1.
- Exit Visual Basic, and save the .vbg as "Group1" file when prompted.
- Restart Visual Basic and open Group1.vbg - note that the Project Explorer's glyphs indicate that one .vbp is source controlled, while the other is not. The project that is not source controlled normally has a glyph indicating that it is read-only.
Keywords: kbinterop kbprb KB174650
