Search

VSS 2005 add-in for VB6 does not display glyphs unless all files in the project are in VSS. by MarkHurd

Closed
as Won't Fix Help for as Won't Fix

0
Sign in to vote
1
Sign in to vote
Sign in
 to vote
Type: Bug
ID: 196185
Opened: 9/6/2006 10:38:50 AM
Access Restriction: Public
2
Workaround(s)
0
User(s) can reproduce this bug
VSS 2005 Add-in for VB6 does not display glyphs showing shared & checked in/out status for VB6 projects that have any file not 'stored' in VSS, such as a resource file, or any related document, let alone source code not worth checking in yet.
Details (expand)
Product Language
English
Version
Other
Operating System
Windows Server 2003
Operating System Language
English
Category
\Lifecycle Tools
Subcategory 1
\Source Code Control
Subcategory 2
\Visual Source Safe
Subcategory 3
\
Steps to Reproduce
0. Open VB6, with VSS2005 add-in enabled.
1. Create a VB6 project with two source files.
2. Save the project, and choose to check in the VB6 project file and one of the source files into VSS.
3. Close and reopen the project.
4. Checkout the VB6 project file.
4. Remove the file not checked in from the VB6 project.
5. Refresh the VSS file status (Tools > SourceSafe > Refresh File Status).
Actual Results
After step 2 you see no checkboxes (though I think I have seen them sometimes here).
After step 3 you see no checkboxes.
After step 5 you see the checkbox next to the file in VSS.
Expected Results
The display after steps 2 and 3 should be: a checkbox next to the checked in file, and nothing next to the other file.
File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 3/14/2007 at 7:56 AM
Thanks for reporting this. It has been assigned to the SourceSafe Integration team for investigation.
Posted by Microsoft on 4/18/2007 at 5:25 PM
Mark,

This is not a supported scenario - it may work, but we don't directly test VSS2005 and VB6 integration.
You could revert back to an older version of VSS, or upgrade to a newer version of VB that is hosted in the Visual Studio shell.

Thanks for your feedback
-Brad Peterson
Visual Studio Source Control Integration Test Lead
Posted by MarkHurd on 4/18/2007 at 10:59 PM
OK, any chance you can release the source code of vbscc.dll to let us fix it ourselves?
© 2010 Microsoft Corporation. All rights reserved. Microsoft Connect Terms of Use | Trademarks | Privacy Statement