The information in this article applies to:
SUMMARYThis is a copy of the Visual Studio 97 Service Pack 1 Readme (English language version). MORE INFORMATIONThe Microsoft Visual Studio 97 Service Pack 1The Microsoft Visual Studio 97 Service Pack 1 upgrades the following Visual Studio applications:
Installing the Microsoft Visual Studio 97 Service Pack 1To install the Service Pack, insert the CD into your computer's CD-ROM drive. If you have downloaded and decompressed the Visual Studio 97 Service Pack 1 or if the Visual Studio 97 Service Pack 1 setup does not automatically launch, go to the root directory of the Visual Studio 97 Service Pack 1 and run setup. The setup.exe will detect the language of your computer's operating system and run one of the following setups:
The Visual Studio 97 Service Pack 1 detects any installed Visual Studio
applications and the specific languages those applications use. (Files are
checked for language which is determined by the operating system settings
and the individual file settings.) The Visual Studio 97 Service Pack 1
supports the following languages: English, French, German, Italian,
Japanese, Korean, Simplified Chinese, Spanish, and Traditional Chinese.
During the installation, the Visual Studio 97 Service Pack 1 displays the files to be installed or updated based on the installed applications detected. After updating your installation of any of the Visual Studio applications, the Visual Studio 97 Service Pack 1 appends any actions to the VS97SP1.log file, which is stored in the root or temporary directory. If you run the Visual Studio 97 Service Pack 1 again, any additional file updates are appended to the end of the log file. Notes on Fixes in the Visual Studio 97 Service Pack 1Do Not Use the Microsoft Utility RegClean 4.1 with Visual Studio or Any Visual Studio Applications:If you run RegClean 4.1 (build 97.71), you might find (if you have Visual C++ Enterprise or Visual Basic Enterprise installed) that the Database Designer no longer works or (if you have Visual InterDev installed) the Database Designer and LinkView tools no longer work. If you have run RegClean, then reinstall the Visual Studio applications as appropriate. Active Server Pages (ASP) Browser Component Does Not Recognize the Browser: If you are installing a new release of Internet Explorer or Netscape, the ASP browser component object may not work in Visual Studio. The string identifying the browser may not be present in the browsecap.ini file, which is located on the Web server. The solution is to either manually change the file or download a newer version of the file from the Internet Information Server (IIS) Web site. The version of the browsecap.ini file that currently ships with the Visual InterDev server components does not recognize Internet Explorer 3.02 as a valid browser. This results in an error when running an .asp page using the browser component in Internet Explorer 3.02. An updated version of the browsecap.ini file, as well as a 1.0b updated version of Active Server Pages, is available at: http://www.microsoft.com/iis/Once there, click the "get IIS" button and choose "Other free software," then "Updates for IIS." Choose a new compressed or uncompressed browsecap.ini file to download. A full download of Active Server Pages English 1.0b is available under "get iis" as well. The 1.0b English version provides full DBCS enabling and some fixes. Updates to SQL Server and Visual Database Tools: We recommend downloading SQL Server Service Pack 3 if you are working with Visual Database Tools and/or Visual InterDev. The SQL Server Service Pack 3 is available at: http://www.msdn.microsoft.comSQL Server Service Pack 3 fixes several issues with the relational engine of Visual Database Tools including:
Internet Explorer Security Options and InfoViewer: InfoViewer, the integrated online documentation viewer included with MSDN and Visual Studio, relies on the Internet Explorer security settings for active content. The online documentation included with MSDN and Visual Studio includes some active content. If you set your Internet Explorer security's maximum security options while browsing the World Wide Web, some types of hyperlinks in your online documentation will not work. Allowing Internet Explorer to download an ActiveX control and then automatically executing the downloaded code is a legitimate security concern. However, you can protect against this problem and still use the online documentation included with MSDN and Visual Studio. To do so, complete the following steps:
Visual C++ for Windows CE customers may experience problems with the Visual Studio family of products. Visual C++ for Windows CE is not currently supported with the Visual Studio Service Pack. If you want to install any part of the Visual Studio 97 Service Pack 1, please uninstall Visual C++ for Windows CE first. If you encounter any problems using Visual C++ for Windows CE with Visual Studio, please call Visual C++ for Windows CE product support. Updating Visual C++ .map Files: Visual Studio 97 Service Pack 1 updates the following .map files if you installed them in your system or system32 directory with Visual C++ 5.0. If you installed these .map files to a different location, used some derivative of these files, or used the .map files directly from the Visual C++ 5.0 CD, you will need to update these files manually or reference them directly from the Visual Studio 97 Service Pack 1 CD. You can find the Visual Studio 97 Service Pack 1 updates to these files in the \all\vc\debug directory on the Visual Studio Service 97 Pack 1 CD.
Finding More Information on Issues Resolved with the Visual Studio 97 Service Pack 1The Microsoft Knowledge Base contains articles that provide more in-depth information about the issues with Visual Studio that are fixed in the Visual Studio 97 Service Pack 1. To locate these articles, go to http://support.msdn.microsoft.com/support/ and then follow the instructions below to build a query.To build a Visual Studio 97 Service Pack 1 query:
http://www.msdn.microsoft.com/search/qrylang.htm. Visual Studio Microsoft Knowledge Base Articles
Visual Basic 5.0 Microsoft Knowledge Base Articles:
The fixes shown below address the problems in dbgrid32.ocx, msrdc20.ocx, and msrdo20.dll related to data-binding and other issues. Also included are fixes for the incompatibility problems with comctl32.ocx. There is also an update to the Visual Basic 5 Setup Kit and some of the .cab files for the ActiveX component download. These .cab files are not installed by the Visual Studio 97 Service Pack 1 but are included on the Visual Studio 97 Service Pack 1 CD.
Visual Database Tools Microsoft Knowledge Base Articles:
Visual SourceSafe Microsoft Knowledge Base Articles:
Visual J++ Microsoft Knowledge Base Articles:
Visual InterDev Microsoft Knowledge Base Articles:
Visual C++ Microsoft Knowledge Base Articles:
The fixes for the Active Template Library (ATL) shown below address the
most commonly reported issues: MBCS compatibility, container compatibility
issues, and internal coding errors in ATL.
The fixes for the compiler shown below address the most commonly reported
COM issues. These issues include: support for Visual Basic-created
controls, internal coding issues in the COM headers, and problems related
to smart pointers and reference counting.
Additionally, there are fixes for templates that contain improper
propagation of the "const" qualifier, and fixes for a problem of forcing
instantiation of all template member functions regardless of whether they
were actually used.
There were also reported problems with either floating-point optimizations,
the global optimizer (/Og) or both. All these reported issues have been
addressed in the Visual Studio 97 Service Pack 1.
Listed below are the Linker fixes that correct a reported problem that ICF
(Identical COMDAT Folding) was causing severe build time losses. The fixes
also remove size limits that were imposed on the size of an executable and
raise the maximum size of the ILK file used by the linker to 64 MB.
The fixes for the Microsoft Foundation Classes (MFC) listed below deal with
the most commonly reported issues that prevented binary compatibility with
MFC 4.2 (shipped with Visual C++ 4.2). These issues included unintended
dependencies on the latest comctl32.dll, the 3.0 version of odbc32.dll,
threading issues and internal coding errors in MFC.
REFERENCESFor additional information, please see the following articles in the Microsoft Knowledge Base: Q170365 INFO: Visual Studio 97 Service Pack 1 - What, Where, and Why Additional query words: kbVBp500 kbVBp kbWinCE100 wince kvVS97sp1 kbVS97sp2 kbVS97SP3 kbreadme
Keywords : kbreadme kbVS97sp1fix kbVS97sp2fix kbGrpDSTools |
Last Reviewed: January 19, 2000 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |