Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
INFO: Visual Studio 6.0 SP3 Readme: Part 6 - Visual InterDev
Article ID: 230730 - View products that this article applies to.
This article was previously published under Q230730
This Readme file contains updated information for the entire Microsoft Visual Studio suite of developer tools. If you downloaded a Core service pack from the Internet, not all sections of this file apply to the updates you received. The fixed issues appropriate for the Core downloads are those listed in the Visual Studio section plus the sections for the products updated by your Core download.
The Microsoft Visual Studio 6.0 Service Pack 3 Readme contains the following sections:
PART 1: Overview and Installation
PART 2: Visual Studio
PART 3: Visual Basic
PART 4: Visual C++
PART 5: Visual FoxPro
PART 6: Visual InterDev
PART 7: Visual J++
PART 8: Visual SourceSafe
PART 9: File Versions
For the latest product information, see the Visual Studio Web site at:
For the latest product updates, see the Visual Studio Support Highlights site at:
Please see the REFERENCES section below for more information about the other parts of this readme.
Microsoft Visual InterDev
Connecting to a SQL ServerIf you will be using MDAC 2.1 to connect to a SQL Server, you must run the version of instcat.sql installed with MDAC 2.1 SP1, which can be found in your system directory.
To run instcat.sql:
Internet Explorer 5Installing Internet Explorer 5 is strongly advised. Using Internet Explorer 5 with Visual InterDev 6.0 provides enhanced HTML editing and other benefits. Internet Explorer 5 is provided on the Visual Studio 6.0 Service Pack 3 CD in the IE5 folder under your language folder. It is also available from the Microsoft Windows Technologies Internet Explorer Home Page at:
"NT SP4 not tested" MessageDuring the Visual InterDev 6.0 installation, if you are installing the NT Option Pack onto Windows NT 4.0 with Service Pack 4, you might see the message "We haven't tested this on NT SP4, do you want to continue?" You should reply "Yes" to this message.
Working with Windows NT 4.0 Service Pack 4Since Visual InterDev 6.0 was released, Service Pack 4 has become available for Windows NT. It is recommended you install Service Pack 4 on your Windows NT Server computer. Windows NT 4.0 Service Pack 4 is available from the Microsoft Windows Update page.
The availability of Windows NT Service Pack 4 requires slight changes to the installation instructions published in the Visual InterDev 6.0 Readme file (ReadmeVI.HTM). In general:
Corrections to the Visual InterDev 6.0 Readme installation instructions (ReadmeVI.HTM)Because Windows NT 4.0 Service Pack 4 is now available, the following installation instructions replace the corresponding instructions in the Visual InterDev 6.0 Readme file (ReadmeVI.HTM).
Client Installation: If You Are Installing on Windows NTThe following components are required for the PageNavbar design-time control, remote debugging, and previewing active server pages on your local machine. You may choose not to select these components if you do not want to take advantage of these features.
Server Installation for Windows NTPerform the following steps if you are installing the server on Windows NT:
Changes to Data ConnectionsData connections can now be established using OLE DB data source providers, which offer greater flexibility in data sources and more efficient connections. For data sources that do not yet support OLE DB providers, you can continue to use ODBC-based connections.
For more details, see the topic "Connecting to a Database" in the Visual InterDev 6.0 SP3 documentation.
Changes to the HTML Editor
New GlyphsThe glyphs used to mark non-visual elements differ depending on whether the editor is being used with Microsoft Internet Explorer 4.0 or Internet Explorer 5. The glyphs used with Internet Explorer 4 are described in the documentation that accompanies Visual InterDev. The following table lists the glyphs the editor can display if Internet Explorer 5 is installed on the computer.
Improved White Space PreservationIf you are using Internet Explorer 5, Visual InterDev can do a better job of preserving the exact layout of an HTML file when filtering elements that require special handling, such as scripts and design-time controls (DTCs).
See also Exceptions to white space preservation later in this document.
Debugging ASP Script ObjectsA new debugging feature has been added to the scripting object model that allows you to catch errors that occur in lower-level components (such as during database access), trace events, and display warnings when script objects encounter possible errors. For more information about debugging and the scripting object model, see the topic "Debugging Script Objects in ASP Pages" in the documentation that accompanies Visual InterDev 6.0.
Enabling ASP Script Object DebuggingThe documentation for ASP script object debugging incorrectly says that the following script block is automatically added to an .asp page when you first create the page:
This is incorrect. The script block is not added to the page until you enable the scripting object model for that page.
Adding Debugging to Existing ApplicationsThe new script object debugging features are automatically available when you create new webs in Visual InterDev 6.0. However, they are not automatically added to your existing applications. To take advantage of the debugging features, you must update the script libraries in your applications (projects) and update individual .asp pages, as described in the following procedures: To update script libraries in an existing application:
To Add Script Object Debugging to an Individual .asp Page
Localized Error Messages for the Script LibraryIf an error occurs inside the script library when you are using Visual InterDev design-time controls, the resulting error message is displayed in English, along with an error number. You may look up the translated error text by error number. Translated versions of these error messages are available in SLErrors.htm on the Service Pack 3 CD under the appropriate language subdirectory in the \support folder. If you downloaded the service pack, SLErrors.htm is located in the folder in which you extracted the files.
Other FixesThe following problems have also been fixed in Visual Studio 6.0 Service Pack 3. The "Q" number that precedes most fixes indicates the ID of a Knowledge Base article that provides further details about the problem and the fix:
Exceptions to white space preservation in HTML editorWhen you load a document into the HTML editor or switch between Design view and Source view, the editor attempts to preserve the format of the document as closely as possible. However, this is not always possible. If you are using Internet Explorer 5, the following changes might be made to the document:
Individual Themes Deleted During RecalculationWhen using source control to obtain files that belong to a theme, always perform a Check Out or Get Local on all files in the theme. You can do this by selecting a theme folder before getting the files. Otherwise, if part of a theme is local and the remainder is on the server, you might encounter problems. Recalculating links or switching from local to master mode might cause the theme to be deleted from your project. Likewise, check all files back in at the same time.
RDS Objects on Page Cause "failed to load" MessageIf a page contains an <OBJECT> tag that references an RDS component, when you switch to Source view in the HTML editor, you will see the message:
This occurs because the RDS objects do not have a visual representation, so Source view cannot render them. However, the objects will function correctly.
Some objects have failed to load. The objects will be displayed as text.
For more information about the Visual Studio 6.0 SP3 readme, please see the following articles in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/230722/EN-US/ )Visual Studio 6.0 SP3 Readme Part 1 - Overview and Installation
(http://support.microsoft.com/kb/230724/EN-US/ )Visual Studio 6.0 SP3 Readme Part 2 - Visual Studio
(http://support.microsoft.com/kb/230726/EN-US/ )Visual Studio 6.0 SP3 Readme Part 3 - Visual Basic
(http://support.microsoft.com/kb/230727/EN-US/ )Visual Studio 6.0 SP3 Readme Part 4 - Visual C++
(http://support.microsoft.com/kb/230729/EN-US/ )Visual Studio 6.0 SP3 Readme Part 5 - Visual FoxPro
(http://support.microsoft.com/kb/230731/EN-US/ )Visual Studio 6.0 SP3 Readme Part 7 - Visual J++
(http://support.microsoft.com/kb/230732/EN-US/ )Visual Studio 6.0 SP3 Readme Part 8 - Visual SourceSafe
(http://support.microsoft.com/kb/230733/EN-US/ )Visual Studio 6.0 SP3 Readme Part 9 - File Versions
Article ID: 230730 - Last Review: August 27, 2001 - Revision: 1.0