INFO: Readme.wri: Section 5, New Features of Visual SourceSafe

 Last reviewed: February 28, 1997
Article ID: Q139362 
4.00    | 4.00       | 4.00
WINDOWS | WINDOWS NT | MS-DOS kbreadme

The information in this article applies to:

  • Microsoft Visual SourceSafe for Windows, version 4.0
  • Microsoft Visual SourceSafe for Windows NT, version 4.0
  • Microsoft Visual SourceSafe for MS-DOS, version 4.0
  • Standard, Professional, and Enterprise Editions of Microsoft Visual Basic for Windows, 16-bit and 32-bit, version 4.0

SUMMARY

This article holds part 5, New Features of Visual Sourcesafe 4.0, of the Readme.wri file. For more information about other sections of the Readme.wri file, please see the following articles in the Microsoft Knowledge Base: 

  ARTICLE-ID: Q139358
  TITLE     : Readme.wri: Section 1.Software Installation Information

  ARTICLE-ID: Q139359
  TITLE     : Readme.wri: Section 2, General Notes and Tips

  ARTICLE-ID: Q139361
  TITLE     : Readme.wri: Section 3, Issues and Considerations

  ARTICLE-ID: Q139360
  TITLE     : Readme.wri: Section 4, Documentation Notes

MORE INFORMATION

New features of Visual SourceSafe 4.0 include:

Integration

Visual SourceSafe can now be integrated into Visual Basic 4.0 (Enterprise and Professional editions) and a Microsoft Developer Studio product. From inside those environments, the user has access to all the common Visual SourceSafe commands without leaving the IDE.

New Look and Feel

Older versions of Visual SourceSafe were designed to look like the Microsoft Windows 3.1 File Manager. Visual SourceSafe 4.0 is designed with the look and feel of the Microsoft Windows 95 Explorer. Other visual enhancements include tab dialog boxes for Options and Properties, friendlier menu names, and a redesigned toolbar with tool tips.

Long Filenames

Visual SourceSafe 4.0 supports file and project names up to 255 characters, with project paths up to 259 characters. Usernames, labels, and other strings have also been expanded.

Working Directory

Visual SourceSafe's handling of the Working Directory, the most common cause of confusion in Visual SourceSafe 3.x, has been vastly improved in 4.0. If a user has not designated a working directory for a project, no "default" working directory is assigned. You must specify a working directory to use certain commands, such as Get and Check Out. In addition, the working directory display has been moved to a more prominent location above the file list in the Visual SourceSafe Explorer.

International Support

Visual SourceSafe 4.0 supports international date/time formats and will be localized into languages used around the world.

KBCategory: kbreadme
KBSubcategory: SourceSafe ssvb vss vbwin
Additional reference words: 4.00
Keywords : SourceSafe ssvb vbwin vss kbreadme
Version : 4.00 | 4.00 | 4.00
Platform : MS-DOS NT WINDOWS

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: February 28, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.