Explore topic-wise InterviewSolutions in .

Microsoft discourages the use of the SSSCC API. Instead they propose you use the OLE Automation interface. 

 However, if you still WISH to use the API you can request the MSSCCI SPEC by writing to msscci@microsoft. They will send you the NDA you need to SIGN to get the spec, and then send you the spec.

Microsoft discourages the use of the SSSCC API. Instead they propose you use the OLE Automation interface. 

 However, if you still wish to use the API you can request the MSSCCI spec by writing to msscci@microsoft. They will send you the NDA you need to sign to get the spec, and then send you the spec.

It would appear that the information provided in the FP2K user guide with respect to integrating FP2K and Visual Safe inadvertently APPLIES to the PREVIOUS version (FrontPage 98) and not FP2K. 

The FOLLOWING instructions should help in setting up FrontPage 2000:

1. USE FrontPage 2000 to create your web
2. Add the web folder to VSS as a new VSS Project 
3. Set the VSS Project as a Web Project in VSS Administrator 

It would appear that the information provided in the FP2K user guide with respect to integrating FP2K and Visual Safe inadvertently applies to the previous version (FrontPage 98) and not FP2K. 

The following instructions should help in setting up FrontPage 2000:

CERTAINLY, check out Web Projects and Control INTEGRATION in VISUAL Studio .NET.

Certainly, check out Web Projects and Control Integration in Visual Studio .NET.

CHECK out KBA Q180945, "HOW TO DISCONNECT a PROJECT from CONTROL"

Check out KBA Q180945, "HOW TO Disconnect a Project from Control"

You can coax/encourage USERS but it is VIRTUALLY IMPOSSIBLE to FORCE them.

You can coax/encourage users but it is virtually impossible to force them.

Search MS ONLINE SUPPORT, VISUAL Safe, for any of the following keywords, depending on the version of Visual Studio you are using and the SERVICE Pack in which you want to RESEARCH kbVS97sp1, kbVS97sp2, kbVS97sp3, kbVS600sp1, kbVS600sp2, kbVS600sp3, kbVS600sp4, kbVS600sp5

Search MS online support, Visual Safe, for any of the following keywords, depending on the version of Visual Studio you are using and the Service Pack in which you want to research kbVS97sp1, kbVS97sp2, kbVS97sp3, kbVS600sp1, kbVS600sp2, kbVS600sp3, kbVS600sp4, kbVS600sp5

VSS 6.0 supports some ADMINISTRATIVE functions. READ the SPECIFICATION and look at the SAMPLES.

VSS 6.0 supports some administrative functions. Read the specification and look at the samples.

You can do this USING the command-line PIN parameter and the wildcard character for the file NAME.

For EXAMPLE

SS PIN $/MyProject/*.* -VLver1

You can do this using the command-line pin parameter and the wildcard character for the file name.

For example

SS PIN $/MyProject/*.* -VLver1

CHECK out KBA Q192625, PRB VC++ SHARED WORKSPACE File Loses Project Locations.

Check out KBA Q192625, PRB VC++ Shared Workspace File Loses Project Locations.

Use the SSARC and SSRESTOR programs. Version 6.0 has a GUI interface to these programs making them easier to use. Also, be careful when RESTORING to a database that was created by COPYING an EXISTING database and then deleting all files and projects in it READ Q176780 - Use Guidscan.exe to View or CHANGE GUID in a VSS Database .

Use the SSARC and SSRESTOR programs. Version 6.0 has a GUI interface to these programs making them easier to use. Also, be careful when restoring to a database that was created by copying an existing database and then deleting all files and projects in it Read Q176780 - Use Guidscan.exe to View or Change GUID in a VSS Database .

1. Set the product to VisualSafe 
2. Set the search option to KEYWORDS 
3. Enter kbbug for the QUESTION

Use the supplied conversion utility pvcs_ss.exe. NOTE that this will not work with long file NAMES, and it does not work with logfiles created by the NT version of PVCS. See KBA Q140362 

Use the supplied conversion utility pvcs_ss.exe. Note that this will not work with long file names, and it does not work with logfiles created by the NT version of PVCS. See KBA Q140362 

Analyze.exe is Visual Safes database maintenance program. This should be run regularly (suggestions range from nightly to monthly). It can repair DAMAGED databases as long as no USERS are logged on (USE the -f command line option). It also has an option for deleting unused files, which will recover space taken up in the database by files and projects that have been purged (-d option). A compress option, -c, will PERFORM some COMPRESSION on the database where possible. 

Analyze.exe is Visual Safes database maintenance program. This should be run regularly (suggestions range from nightly to monthly). It can repair damaged databases as long as no users are logged on (use the -f command line option). It also has an option for deleting unused files, which will recover space taken up in the database by files and projects that have been purged (-d option). A compress option, -c, will perform some compression on the database where possible. 

This REQUIRES that you iterate through each version of the file looking for the label you WANT. Once the CORRECT version of the file is identified you can retrieve the comment for that version. Below is some sample VB code demonstrating this

For Each objVSSVersion In objVSSObject.Versions

If objVSSVersion.Action = "BETA 1" Then

MsgBox(objVSSVersion.LabelComment)

END If

Next

This requires that you iterate through each version of the file looking for the label you want. Once the correct version of the file is identified you can retrieve the comment for that version. Below is some sample VB code demonstrating this

For Each objVSSVersion In objVSSObject.Versions

If objVSSVersion.Action = "Beta 1" Then

MsgBox(objVSSVersion.LabelComment)

End If

Next

• Make sure that the srcsafe.ini variable Keyword_Masks is set to the appropriate file types you WANT to expand keywords in. (e.g. Keyword_Masks=*.cpp,*.h,*.idl)
• Remember that the keywords are case SENSITIVE and include a colon at the end $History$
• If you're using something that generates multiple lines, like $History$, you need to have the SECTION [KEYWORD Comments] set up to proper VALUES for commenting out each line.

CHECK out the NEWSGROUP posting HOWTO RESET VSS 6 Admin Password by PAUL Gurtler.

Check out the newsgroup posting HOWTO Reset VSS 6 Admin Password by Paul Gurtler.

• Make SURE that no one is using the database and that ANALYZE will not begin to run while you are backing up the database. Use any backup utility to copy the DATA, LABELS, and USERS directories.
• See Chuck Kollars web site for further suggestions and a sample .BAT file to secure and backup the database.
• Some VSS administrators have SUGGESTED using SSARC as a way to backup the database. Use SSARC -d- <archive file> $/ to archive without deleting any files.

No. The USERS NT logon NAME is USED by default when STARTING VSS but this is the only integration. All NT users who wish to use VSS as well need to be added separately by the VSS administrator.

For information about required network rights CHECK out Q131022 - INFO Required Network Rights for the Safe Directories.

No. The users NT logon name is used by default when starting VSS but this is the only integration. All NT users who wish to use VSS as well need to be added separately by the VSS administrator.

For information about required network rights check out Q131022 - INFO Required Network Rights for the Safe Directories.

MICROSOFT has a web PAGE LISTING some best practices, and another page containing their own VERSION.

Microsoft has a web page listing some best practices, and another page containing their own version.

This one is not intuitive. From within the VSS Explorer, PERFORM the following steps (Steps are for VSS 6.0. Steps are similar for 4.0 and 5.0) 

1. Select the project that has the label that you want to rename. 
2. Click on the SHOW History BUTTON. 
3. CHECK Include Labels and Show Labels 
4. Uncheck Include File Histories and optionally select a date to search back to. Click OK. 
5. In the History dialog box, find and select the label.

This one is not intuitive. From within the VSS Explorer, perform the following steps (Steps are for VSS 6.0. Steps are similar for 4.0 and 5.0) 

Under the REGISTRY key HKEY_CURRENT_USERSoftwareMicrosoftDevStudio6.0 CONTROL (for Visual Studio 6.0) or HKEY_CURRENT_USERSoftwareMicrosoftDevStudio5.0 Control (for Visual Studio 5.0) , CHANGE or CREATED the entry

Name Disabled

Type REG_DWORD

DATA 0x1

Under the registry key HKEY_CURRENT_USERSoftwareMicrosoftDevStudio6.0 Control (for Visual Studio 6.0) or HKEY_CURRENT_USERSoftwareMicrosoftDevStudio5.0 Control (for Visual Studio 5.0) , change or created the entry

Name Disabled

Type REG_DWORD

Data 0x1

• For 5.0 VS. 4.0 COMPATIBILITY, read KBA Q176553
• Version 6.0 can read and write 5.0 databases, and has an option to upgrade or use a new database FORMAT. Using this new format gives you the new LABEL promotion FEATURE, but cannot be read by anything earlier than 6.0. There are also some performance enhancements with the new 6.0 version of the database.

These events are not SUPPORTED as of this POSTING by Rich KNOX of Microsoft TRAPPING Rollbacks/Deletions. 

These events are not supported as of this posting by Rich Knox of Microsoft Trapping Rollbacks/Deletions. 

NEED to USE the '-v' SWITCH with an 'L' after it to indicate a label (-R is for recursive)

SS GET $project -VLmylabel -R

Need to use the '-v' switch with an 'L' after it to indicate a label (-R is for recursive)

SS GET $project -VLmylabel -R

VSS 6.0 fully supports LABEL comments. Label comments, HOWEVER, are not AVAILABLE in VSS 5.0. For more INFORMATION check out KBA Q176353 http//support.microsoft/support/kb/articles/q176/3/53.asp

VSS 6.0 fully supports label comments. Label comments, however, are not available in VSS 5.0. For more information check out KBA Q176353 http//support.microsoft/support/kb/articles/q176/3/53.asp

• VSS Integration with VISUAL FoxPro
• To search for articles RELATING to Visual FoxPro integration, search for the KEYWORD SSFOX. Also check out VisualSafeIntegration.
• VSS integration with Access
• To search for other articles relating to Access integration, search for the keyword SSACC
• VSS Integration with Office products

This one is not INTUITIVE. From WITHIN VSS Explorer, select the project, show history, check Labels Only, find the label of interest, click on DETAILS, select the label text and delete it. Click CLOSE, which will ask if you are sure you want to change the label. Click YES and you're done.

This one is not intuitive. From within VSS Explorer, select the project, show history, check Labels Only, find the label of interest, click on Details, select the label text and delete it. Click Close, which will ask if you are sure you want to change the label. Click Yes and you're done.

• ELSINORE Technologies has a product called Visual Intercept
• SEE MetaQuest's Census
• See DevTrack from www.techexcel 
• Check out a Visual C++/Safe CHANGE and Build TRACER at http//www.codeguru/devstudio_macros/tracer.html

•  From SS Explorer select the project folder which contained the deleted file. 
• When on a project folder, click on Show PROPERTIES, then select the Deleted Items Tab.
• Find the deleted file and click on Recover.
• From the command line use the SS GET command on the parent project. Do not list the files or use *.* in the get.
• For EXAMPLE: the FOLLOWING command will get files including deleted files.
• SS GET $MASTERPROJ1 -VLOldLabel 

This could be caused by having too many Dir= or Shadow= entries in one of the ini files. Try to create a directory structure on disk which matches the VSS project tree. Then clean up the extra Dir= and Shadow= entries in the .ini files. That way you only need an ENTRY in your ini FILE for each TIP project. 

If you find that VC++ is very slow now that you're using the VSS integration, deleting the .NCB file before opening the WORKSPACE might help. VC++ 6.0 doesn't have this.

This could be caused by having too many Dir= or Shadow= entries in one of the ini files. Try to create a directory structure on disk which matches the VSS project tree. Then clean up the extra Dir= and Shadow= entries in the .ini files. That way you only need an entry in your ini file for each tip project. 

If you find that VC++ is very slow now that you're using the VSS integration, deleting the .NCB file before opening the workspace might help. VC++ 6.0 doesn't have this.

Create a zero-byte file CALLED admin.lck in the [SHARE]dataloggedin folder and the DATABASE is locked. Delete it when ANALYZE is done to unlock. NOTE that this will not kick out currently logged in users.

Create a zero-byte file called admin.lck in the [share]dataloggedin folder and the database is locked. Delete it when Analyze is done to unlock. Note that this will not kick out currently logged in users.