| Microsoft Year 2000 Readiness Disclosure & Resource Center |
|
|
| Visual SourceSafe 5.0 (Spanish) - 32-Bit Win
| Product Summary |
Product: Visual SourceSafe
Version: 5.0 |
Category: Compliant*#
Operating System: 32-Bit Win |
| Language: Spanish |
Release Date: 01 Oct 1996 |
| Operational Range: |
01 Jan 1940 - 18 Jan 2038 |
| Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes |
| Prerequisites: |
Visual SourceSafe 5.0 Year 2000 update (history issue) |
| Product Dependencies: |
None |
| Clock Dependencies: |
Operating System Clock |
| Last Updated: |
28 Sep 1999 | |
| Product Details |
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement?
Yes.
How the product runtime handles dates:
Visual SourceSafe 5.0, as originally shipped, has a known issue when attempting to pull the history of a file or project filtered by user specified dates. This issue can be summarized as:
- In the History pre-dialog where one can specify a date range to do a history on ("show the History between 1/1/97 and 2/24/2000), if a date is specified after the year 2000, it will be treated as a date in the 1900Æs. The same issue exists on the command line.
- The history pre-dialog in version 5.0 doesnÆt accept 4-digit years.
The issues described above are cosmetic display issues and do not impact the storage of files or project data. This data is stored correctly and clock rollover to the year 2000 will not cause data loss. The history report issue does not have an impact on the applications that developers build using Visual SourceSafe as the source code control tool. Only the ability to view history where a date is specified is affected.
The most restrictive structure Visual SourceSafe uses for dates is a long integer containing the number of seconds since January 1, 1970.
BIOS dependencies in Visual SourceSafe:
Visual SourceSafe uses a "time stamp" to data files. This time stamp contains date information obtained from the system clock. The time stamp is provided by the machineÆs BIOS (Basic Input-Output System), and is not provided by Visual SourceSafe. If the machine uses a year 2000 non-compliant BIOS/RTC that fails to reset the system clock to January 1, 2000 (and if the operating system does not automatically correct the date) new files and new versions will be saved with incorrect time stamps. This could corrupt data in the history database. For example, if the version control system checks in a "new" file with an incorrect date (say, a year in the 1900s), the control system could overwrite the "new" version with an older version of the data file. Developers should contact their PC vendor to ensure that the computer's BIOS is year 2000 compliant.
Two-digit shortcut handling:
Years 00 û 38 for dates 1/1/00 through 1/18/38 are converted to 2000 û 2038.
Years 38 û 99 for dates 1/19/38 through 12/31/99 are converted to 1938 û 1999.
Recommended practices to develop year 2000 compliant applications:
The history report issue does not have an impact on the applications that developers build using Visual SourceSafe as the source code control tool. Only the ability to view history where a date is specified is affected.
Developers should contact their PC vendor to ensure that the computer's BIOS is year 2000 compliant. This issue does not impact the ability of developers to build year 2000 compliant applications.
Common development errors dealing with year 2000 date issues:
The history report issue does not have an impact on the applications that developers build using Visual SourceSafe as the source code control tool. Only the ability to view history where a date is specified is affected.
Testing guidelines and recommendations:
Customers should not need to change their behavior outside of the History pre-dialog that has the minor issues described above.
An update for Visual SourceSafe version 5.0 to resolve the history report issue can be found at
http://msdn.microsoft.com/ssafe/downloads/year2000.asp.
| |
Return to Search Screen
| Legend of Symbols: |
| * |
The product is compliant with recommended customer action. This indicates a prerequisite action is recommended which may include loading a software update or reading a document. |
| # |
The product is compliant with acceptable deviations from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability, or reliability of the product. |
| + |
The product is compliant with pending Year 2000 software updates. Future maintenance actions will be recommended shortly. See Product Guide for further details. |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
If after reviewing this information you have additional questions related to this product, click here.
YEAR 2000 READINESS DISCLOSURE
ALL COMMUNICATIONS OR CONVEYANCES OF INFORMATION TO YOU CONCERNING MICROSOFT AND THE YEAR 2000, INCLUDING BUT NOT LIMITED TO THIS DOCUMENT OR ANY OTHER PAST, PRESENT OR FUTURE INFORMATION REGARDING YEAR 2000 TESTING, ASSESSMENTS, READINESS, TIME TABLES, OBJECTIVES, OR OTHER (COLLECTIVELY THE "MICROSOFT YEAR 2000 STATEMENT"), ARE PROVIDED AS A "YEAR 2000 READINESS DISCLOSURE" (AS DEFINED BY THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT) AND CAN BE FOUND AT MICROSOFT'S YEAR 2000 WEBSITE LOCATED AT http://www.microsoft.com/year2000/ (the "Y2K WEBSITE"). EACH MICROSOFT YEAR 2000 STATEMENT IS PROVIDED PURSUANT TO THE TERMS HEREOF, THE TERMS OF THE Y2K WEBSITE, AND THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT FOR THE SOLE PURPOSE OF ASSISTING THE PLANNING FOR THE TRANSITION TO THE YEAR 2000. EACH MICROSOFT YEAR 2000 STATEMENT CONTAINS INFORMATION CURRENTLY AVAILABLE AND IS UPDATED REGULARLY AND SUBJECT TO CHANGE. MICROSOFT THEREFORE RECOMMENDS THAT YOU CHECK THE Y2K WEBSITE REGULARLY FOR ANY CHANGES TO ANY MICROSOFT YEAR 2000 STATEMENT. EACH MICROSOFT YEAR 2000 STATEMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. CONSEQUENTLY, MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. MOREOVER, MICROSOFT DOES NOT WARRANT OR MAKE ANY REPRESENTATIONS REGARDING THE USE OR THE RESULTS OF THE USE OF ANY MICROSOFT YEAR 2000 STATEMENT IN TERMS OF ITS CORRECTNESS, ACCURACY, RELIABILITY, OR OTHERWISE. NO ORAL OR WRITTEN INFORMATION OR ADVICE GIVEN BY MICROSOFT OR ITS AUTHORIZED REPRESENTATIVES SHALL CREATE A WARRANTY OR IN ANY WAY DECREASE THE SCOPE OF THIS WARRANTY DISCLAIMER. IN NO EVENT SHALL MICROSOFT OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER REGARDING ANY MICROSOFT YEAR 2000 STATEMENT INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS, PUNITIVE OR SPECIAL DAMAGES, EVEN IF MICROSOFT 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 TO YOU. THE INFORMATION CONTAINED IN EACH MICROSOFT YEAR 2000 STATEMENT IS FOUND AT THE Y2K WEBSITE AND IS INTENDED TO BE READ IN CONJUNCTION WITH OTHER INFORMATION LOCATED AT THE Y2K WEBSITE, INCLUDING BUT NOT LIMITED TO MICROSOFT'S YEAR 2000 COMPLIANCE STATEMENT, THE DESCRIPTION OF THE CATEGORIES OF COMPLIANCE INTO WHICH MICROSOFT HAS CLASSIFIED ITS PRODUCTS IN ITS YEAR 2000 PRODUCT GUIDE, AND THE MICROSOFT YEAR 2000 TEST CRITERIA.
ANY MICROSOFT YEAR 2000 STATEMENTS MADE TO YOU IN THE COURSE OF PROVIDING YEAR 2000 RELATED UPDATES, YEAR 2000 DIAGNOSTIC TOOLS, OR REMEDIATION SERVICES (IF ANY) ARE SUBJECT TO THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT (112 STAT. 2386). IN CASE OF A DISPUTE, THIS ACT MAY REDUCE YOUR LEGAL RIGHTS REGARDING THE USE OF ANY SUCH STATEMENTS, UNLESS OTHERWISE SPECIFIED BY YOUR CONTRACT OR TARIFF.
|
