HOWTO: Readme.txt for Visual InterDev 6.0 March Beta 2 Part V

ID: Q230411

The information in this article applies to:

Microsoft Visual InterDev, version 6.0

SUMMARY

The following article contains the complete contents of the Readme.txt file distributed with Microsoft Visual InterDev March Beta, "Beta 2," which shows version 8058 in the About dialog box (selected from the Help menu).

MORE INFORMATION

IISAM Exchange Driver Will Fail If Microsoft Exchange or Microsoft Outlook Is Not Already Installed

The IISAM Exchange driver requires that Microsoft Exchange or Microsoft Outlook be fully installed on your computer prior to installation of Visual InterDev. If neither is installed, the IISAM Exchange driver will not register correctly.

To manually correct the problem after you've installed Visual InterDev, you can install Microsoft Exchange or Microsoft Outlook and then self-register the IISAM Exchange driver using this command line:


regsvr32 msech35.dll

Special Installation Instructions for Computers with Non-U.S. Versions of Microsoft Windows NT 4.0 and Microsoft Internet Explorer

If you are installing this pre-release version of Visual InterDev on a non- U.S. version of Windows NT 4.0, you must first install the appropriate language version of Windows NT 4.0 Service Pack 3.

To install this version of Visual InterDev on a computer that uses an international version of Microsoft Internet Explorer, you must install the appropriate language version of Microsoft Internet Explorer.

The international versions of Windows NT 4.0 Service Pack 3 are available from these locations:

ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes

http://www.microsoft.com/support/winnt/intlsp.asp

The international versions of Microsoft Internet Explorer 4.x are available from:

http://www.microsoft.com/ie/download/

The Version of Microsoft Internet Explorer Shipped with the Visual InterDev March Pre-Release

This pre-release of Visual InterDev ships with a version of Microsoft Internet Explorer 4.01 that includes recent fixes that are required for this pre-release of Visual InterDev to work properly.

Access Database Connection Strings Need Manual Modification

Connection strings for Access databases that are located in the Global.asa file need the following manual modification to function properly:

All single backslash characters ("\") must be replaced with two backslashes ("\\").

Remove the extra semi-colon (";") that appears at the end of the string.

An alternate solution is to place the Access database in the root directory of your drive. For example: C:\Northwind.mdb.

Pressing CTRL+BACKSPACE Below a Control in Source View Might Delete Multiple Lines

When editing in Source view, if you place the cursor below a control and press CTRL+BACKSPACE, the editor may delete multiple lines of text. If this happens, choose Edit menu, Undo to restore the text.

Problems Viewing the Script Outline Window

It is possible that the Script Outline window may disappear. Normally, you would display the Script Outline window by choosing View menu, Other Windows, Script Outline. If the menu command does not work, exit Visual InterDev, delete your Views.prf file, and restart the product.

Remote Deployment to a Server with FAT-Formatted Hard Disk Drive

If the hard disk drive on the server you are using for remote deployment is formatted as a FAT drive, you need to modify the Allow Anonymous Access in Authentication methods option of the Microsoft Management Console (MMC).

On the Windows Start menu, click Programs, Windows NT 4.0 Option Pack, Microsoft Internet Information Server, and then Internet Service Manager to start the Microsoft Management Console.

In the tree view, expand Internet Information Server and <computer name>.

Right-click Default Web Site and select Properties.

On the Directory Security tab, click the Edit button for Anonymous Access in Authentication Control to display the Authentication Methods dialog box.

Uncheck the Allow Anonymous Access option.

Choose OK to close all dialog boxes.

The Limit SQL Output Option Determines the Number of Rows Affected by the INSERT and UPDATE Statements in an SQL Script

To modify the Limit SQL Output setting, choose Tools menu and then Options to display the Options dialog box. Expand Data Tools, Data View on the left. Set Limit SQL output on the right. If this option is not selected, a default of 1024 rows is used.

Problem with Copy Web When Working in Offline Mode

When working in Offline mode, you can choose Project menu, Web Project, and then Copy Web to display the Copy Web dialog box. If you uncheck the Add to existing Web option, an error message will be displayed stating that the local directory does not exist, even though the directory does in fact exist. This problem will be resolved in the next version.

Server-Side Extensions

During server setup, new server-side extensions are installed. In order for these extensions to function properly after setup, you need to recalculate links:

From the directory: "program files\microsoft frontpage\version 3.0\bin" in the command prompt, run Fpsrvadm.exe.

You will be given 14 options. Choose Option 8 (Recalculate links).

You will be asked to "Enter port #." Choose your http port, or press ENTER for the Default (80).

You will be asked to "Enter Web Name." Press ENTER to start recalculation.

Difference in CSS Implementation Between Netscape and Internet Explorer

Netscape Navigator and Communicator versions 4.0 through 4.03 implement Cascading Style Sheets (CSS) differently than Internet Explorer. Navigator interprets relative URLs as relative to the document rather than to the linked CSS file. To work around this difference:

Copy, but do not move, all of the images from the directory of the theme that you are using to the directory that contains the document that references the CSS file.

-or-

Change the relative URLs in your CSS files to the appropriate absolute URLs.

Layouts Implementation Changed from the Last Pre-Release Version

The implementation of Layouts changed between the previous pre-release version of Visual InterDev and the March pre-release version. This change is important to you only if you used Layouts with the previous pre-release version and want to work with them in the March pre-release version.

Previously, Layouts were based on HTML comments. Now, they are based on design-time controls. If you have a Layout that was created in the previous pre-release version and use it in an existing project with the March pre- release version, and if you apply a layout to one of the pages, then you will get duplicate information.

Before applying a Layout in the March pre-release version, remove any layout information that was applied with the previous pre-release version. To do this, do one of the following:

Open the project in the previous pre-release version and apply a "<none>" layout.

Delete existing layout information by hand in each page, including the Layout's HTML comment tags.

Delete pages that use Layouts.

Use Root-Level Default Document Properties Only

If you are running an IIS 4.0 Web server, you may encounter a problem with the ability to set a default document (welcome page) for each directory on your Web server. When using Site Designer, the default document information is taken from the Web server's site-level (root-level) properties and not from the directory-level properties. To work around this, set the default document at the Web server's site-level properties pages.

PageNavbar DTC Orientation and Custom HTM

When using custom HTML with a PageNavbar DTC, in order to control the orientation (horizontal or vertical) of the navigation bar, you must use the PageNavbar DTC's orientation setting.

Do Not Remove the Local Copy of Any Theme That Is in Use

Do not remove the local copy of any theme that is in use. If you do, you might encounter errors when re-applying the same theme.

When editing pages with Layouts in Source view, do not enter text between a Layout comment tag and a DTC tag.

When you apply a layout to a page, a comment tag is added (just after the BODY tag) with the name of the layout that has been applied (for example, ). If you edit the page in Source view, there is a chance you may lose any text that is placed between this comment and the start of the first Layout DTC. To avoid this problem, be sure to enter any text between the BODY tag and the comment, not between the comment and the first layout DTC.

Do Not Convert Layout DTCs to Text

If you convert any of the Layout DTCs (that get added to a page when you apply a layout) to text, all subsequent Layout applications to that page will fail silently. To avoid this problem, don't convert any of the Layout DTCs to text.

Automatic Adding of Projects to Source Control

There is an option on the Tools menu, Options dialog box, Source Control node that allows projects to be automatically added to source control. The default for this option is off. Do not turn on this option or your development environment may crash.

Using the Text Editor of Visual J++ Technology Preview 1 or Visual InterDev on Non-far East versions of Windows 95

If you are using the text editor of the Web release of Visual J++ Technology Preview 1 or the pre-release of Visual InterDev, on nonFar East versions of Windows 95, you may see the text editor window behave differently when you choose nondefault script.

The text editor window may go blank or display only part of the text you have entered if you choose a font with a script that is not the default script. For example, if you change the font from Courier New (Western) to Courier New (Cyrillic) on English Windows 95, you will see only part of the text displayed.

To recover the text, on the Tools menu, click Options, then Reset All. Alternatively, choose a font with a script that matches the system.

Additional query words:

Keywords : kbExtension kbFrontPage kbServer kbVisID600
Version : WINDOWS:6.0
Platform : WINDOWS
Issue type : kbhowto