INFO: Readme.txt for Visual InterDev 6.0

• Microsoft Visual InterDev, version 6.0

SUMMARY

The following article contains the complete contents of the Readme.txt file distributed with Microsoft Visual InterDev.

MORE INFORMATION

The Visual InterDev Readme includes updated information for the documentation provided with Microsoft Visual Studio development System for Windows and the Internet. The information in this document is more up-to- date than the information in the Help system. Many of the issues outlined in this document will be corrected in upcoming releases.

For general installation issues on the Visual Studio 6.0 suite of products, including side by side product installation for installing more than one Visual Studio product on the same computer, see the Installation Notes readme (Install.htm).

For issues that are specific to the Microsoft Visual Database Tools that are installed with Visual InterDev, see the Microsoft Visual Database Tools Readme. For issues on the Help system, see the Microsoft Developer Network (MSDN) Readme.

Contents

• Visual InterDev Installation Notes
  • Installing Visual InterDev
  
  
  
  • Setting up Your Computer for Stored Procedure Versioning through Microsoft Visual SourceSafe and for Stored Procedure Debugging
  
  
  
  • Installing and Running the Sample Application
  
  
  
  • Installing FrontPage 98
  
  
  



• What's New in Visual InterDev



• Known Issues Installation:
  • Uninstalling pre-release versions of Visual InterDev
  
  
  
  • Upgrading Web applications created with a pre-release version
  
  
  
  • Remote Machine Debugging server component must be installed with Windows NT Option Pack
  
  
  
  • Installation problems with the Visual InterDev RAD Remote Deployment Support server component Product Related:
  
  
  
  • Source control does not support file names containing semi-colons
  
  
  
  • Ignore events in the Script Outline view for FRAME, IFRAME, FRAMESET, OPTION
  
  
  
  • Class names containing underscores are not supported
  
  
  
  • The editor does not support "<script>" or "</script>" within JavaScript or VBScript comments
  
  
  
  • Visual InterDev does not support the ActiveMovie control
  
  
  
  • When working offline and editing in Design view, relative URLs of imagefiles must be edited manually
  
  
  
  • Visual InterDev does not support hierarchical recordsets
  
  
  
  • Changes to Client Script Debugging in ASP Pages
  
  
  
  • Browsing "User Notification" sample using Netscape
  
  
  
  • Issue concerning window_onload event not firing
  
  
  
  • "[FrontPage vinavbar component]" appears when browsing a page
  
  
  
  • Difference in CSS implementation between Netscape and Internet Explorer
  
  
  
  • Use server-level default document properties only
  
  
  



• Visual Component Manager
  • "Related Files Tab (Component Properties Dialog Box)" topic incorrect
  
  
  
  • Removing Repository 1.0 Registry Keys
  
  
  
  • Adding repository tables to an existing .mdb file
  
  
  

Visual InterDev Installation Notes

Installing Visual InterDev

1. Insert installation compact disc #1 into your computer.



2. Setup.exe automatically runs the Installation Wizard. The wizard steps you through the installation process. NOTE: Depending on your selections and your current configuration, the wizard will prompt you to install different required components and to reboot Windows one or more times during the installation process. After each reboot, the wizard automatically returns to the proper step.



3. Follow the steps of the Installation Wizard until you are prompted to select either Install Visual InterDev 6.0 or Server Applications.
   • To install the client portion of Visual InterDev, select Install Visual InterDev 6.0 and then see Client Installation below.
   
   
   
   • To install the server portion of Visual InterDev, select Server Applications and then see Server Installation below.
   
   
   
   If you want to install the client and server portions of Visual InterDev on the same computer, begin with the Client Installation.

Client Installation

1. Follow the steps of the Visual InterDev 6.0 Wizard. When prompted, select either a Typical or Custom installation.



2. After the Visual InterDev client has been installed on your computer, you are prompted to install MSDN, the Microsoft Developer Network. Note that you need to install MSDN in order for F1 Help to work and to have access to the Visual InterDev documentation.



3. After MSDN is installed, you arrive at the Server Setup screen.
   • If you are installing the Visual InterDev server on the same computer, stop here and continue with Server Installation below.
   
   
   
   • If you are installing only the Visual InterDev client on the computer, continue with the following steps for Windows NT or Windows 9x.
   
   
   

1. Select Launch BackOffice Installation Wizard and click Install.



2. The BackOffice Installation Wizard will prompt you to select a Custom or Visual InterDev Developer option. Select Custom and click Next.



3. Verify the disk space requirements and click Next.



4. Select Front Page Server Extensions and MS Data Access Components from the top level of the components list.



5. Expand the Windows NT Option Pack node and select:
   • Internet Information Server - for NT Server
   
   
   
   • Microsoft Management Console
   
   
   
   • NT Option Pack Common Files
   
   
   
   • Personal Web Server (PWS) - for NT Workstation
   
   
   
   • Transaction Server
   
   
   



6. Clear the remaining components. As you clear the other components, the wizard might display a message that warns you of various dependencies. You can choose Yes to ignore the dependencies because you are using this computer as a client for Visual InterDev, not as a server.



7. Continue with the remaining steps of the wizard.

1. Select NT Option Pack Common Files and click the Install button. This launches the Microsoft Personal Web Server Setup.
   • When prompted to select Minimum, Typical, or Custom, select Custom. When the list of components is displayed, select the following:
     

     
          Common Program Files
          Microsoft Data Access Components 1.5
          Personal Web Server (PWS)
          Transaction Server 

   
   
   
   • Clear the remaining components. As you clear the other components, the wizard might display a message that warns you of various dependencies. You can choose Yes to ignore the dependencies because you are using this computer as a client for Visual InterDev, not as a server.
   
   
   
   • Continue with the remaining steps of the Personal Web Server Setup.
   
   
   



2. When you return to the Server Setups screen, select FrontPage 98 Server Extensions and click Install.



3. Continue with the remaining steps of the wizard.

Server Installation

Server Installation for Windows NT

1. When prompted by the wizard, select Launch BackOffice Installation Wizard and click Install.



2. The BackOffice Installation Wizard will prompt you to select the Custom or Visual InterDev Developer option. Select the Custom option and click Next.
   
   Select the following options:
   • Windows NT Option Pack 4.0
   
   
   
   • Microsoft Data Access Components
   
   
   
   • Remote Machine Debugging
   
   
   
   • FrontPage Server Extensions
   
   
   
   • Visual InterDev Server
   
   
   



3. Before you click Next, expand the Windows NT Option Pack 4.0 node. In addition to the options selected by default, select the Visual InterDev RAD Remote Deployment Support node. Then expand the Visual InterDev RAD Remote Deployment Support node and select the second instance of Visual InterDev RAD Remote Deployment Support. Make sure that Visual InterDev RAD Remote Deployment Support is selected at both levels.



4. Click Next and continue with the remaining steps of the BackOffice Installation Wizard.



5. The following patch corrects problems related to debugging active server pages and for updating the Global.asa file. After the Installation Wizard has finished, apply this patch.
   • Run \IIS\WinNT\ASP2FIX1.EXE from the installation disc.
     For Visual InterDev Professional version, it's located on CD1.
     For Visual Studio Professional version, it's located on CD2.
     For Visual Studio Enterprise Edition, it's located on CD3.
   
   
   
   • Reboot when prompted.
   
   
   

Server Installation for Windows 9x

1. Select NT Option Pack (for Windows 9x) and click Install. This launches the Microsoft Personal Web Server Setup.
   • When prompted to select Minimum, Typical, or Custom, select Typical.
   
   
   
   • Continue with the remaining steps of the Personal Web Server Setup.
   
   
   



2. Select FrontPage 98 Server Extensions and click Install.



3. Select Data Access Components 2.0 and click Install.



4. Select Visual InterDev Server Components and click Install.



5. Click Next and continue with the remaining steps of the Installation Wizard.



6. The following patch corrects problems related to debugging active server pages and for updating the Global.asa file. After the Installation Wizard has finished, apply this patch.
   • Stop the Web server. In an MS-DOS Prompt window, run the command: pws /stop
   
   
   
   • In the \<windows>\system\inetsrv directory, rename Asp.dll to Asp.old.
   
   
   
   • Copy \IIS\Win9x\Asp.dll from the installation disc to your \<windows>\system\inetsrv directory.
     For Visual InterDev Professional version, it's located on CD1.
     For Visual Studio Professional version, it's located on CD2.
     For Visual Studio Enterprise Edition, it's located on CD3.
   
   
   
   • Restart the Web server. In an MS-DOS Prompt window, run the command:
     pws /start
   
   
   

Production Server Installation for Windows NT

• Windows NT Service Pack 3



• Internet Information Server version 3.0 or later (Visual Studio 6.0 includes Internet Information Server 4.0)



• Data Access Components (to ensure that your application's data-based operations function correctly)



• Visual InterDev server (which installs the proper versions of the scripting engines and the Data Environment run-time files)

1. When prompted by the wizard, select Launch BackOffice Installation Wizard and click Install.



2. The BackOffice Installation Wizard will prompt you to select the Custom or Visual InterDev Developer option. Select the Custom option and click Next.



3. Select the following options:
   • Windows NT Option Pack 4.0
   
   
   
   • MS Data Access Components
   
   
   
   • Front Page Server Extensions - Optional
   
   
   
   • Posting Acceptor (2.0) - Optional
   
   
   
   • Visual InterDev Server
   
   
   



4. Click Next and continue with the remaining steps of the BackOffice Installation Wizard.

Visual SourceSafe and for Stored Procedure Debugging

1. Click Start Menu, Control Panel, and then run Services.



2. Select the service MSSQLServer and click the Startup button.



3. In the Service dialog box, select the option This Account.



4. In the This Account text box type a domain and user name (e.g., "domain\username") that has access to the server where the Visual SourceSafe server is installed. Type a password in the Password text box. Click OK.



5. Stop the MSSQLServer service and then restart it.

To Install the SQL Server Debugging and Visual InterDev Server Components

1. Run the Visual Studio Enterprise Edition setup.



2. When prompted, select Launch BackOffice Installation Wizard and click Install.



3. On the first screen of the BackOffice Installation Wizard, select Custom.



4. When prompted with a list of BackOffice Programs and Their Components, select SQL Server Debugging and Visual InterDev Server.



5. Continue with the remaining steps of the wizard.

Installing and Running the Sample Application

1. In Visual InterDev, if the New Project dialog box isn't visible, choose New Project from the File menu.



2. In the New tab of the New Project dialog box, select the Sample App Wizard icon, enter a name for the project, and choose Open.



3. Follow the steps in the Sample Application Wizard.

Installing FrontPage 98

1. Run \FrontPage\setup.exe from the installation compact disc. NOTE: If you have the Professional version of Visual InterDev, the FrontPage folder is located on CD 1. If you have the Enterprise version of Visual Studio, the FrontPage folder is located on CD 2.



2. When prompted on the Setup Type screen to select a Typical or Custom installation, select the Custom option.



3. On the Select Components screen, make sure that the FrontPage Personal Web Server option is not selected. Visual InterDev does not support the FrontPage Personal Web Server. NOTE: If you choose to install the FrontPage Personal Web Server on your computer, it is required that you first install IIS version 3.0 or later.



4. Continue with the FrontPage installation wizard.

What's New in Visual InterDev

Known Issues

Known Issues: Installation

Uninstalling Pre-Release Versions of Visual InterDev

1. Click Start, Control Panel and then run the Add/Remove Programs applet.



2. Select Microsoft Visual Studio 98 Enterprise Edition.



3. When prompted, select Remove All.



4. After you have finished removing the program, open Windows Explorer and delete all files in the \Program Files\Microsoft Visual Studio folder.



5. Click Start, Run and enter REGEDIT.



6. In the Registry Editor, delete the registry key:
   

   
         HKEY_LOCAL_MACHINE\Software\Microsoft\VisualStudio\6.0. 




7. Delete the registry key:
   

   
         HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\6.0. 

Upgrading Web Applications Created with a Pre-Release Version

1. Create a new Web project.
   When prompted in step 2 of the Web Project Wizard to specify your Web, select Connect to an existing Web application and select your existing Web application from the list box.
   If prompted to create a new script library, choose Yes.
   NOTE: All developers who use this Web application must create a new Web project on their workstations.



2. If your project contains data commands, you need to upgrade them. To do this, display the Data Environment, right-click any data command and choose Refresh.



3. For each page that contains a data-bound control or the PageObject control, you must open the file, switch to Source view, "dirty" it (add and remove a space), switch back to Design view and then save the file.



4. Because the scripting object model has changed, you need to update all ASP pages that had the scripting object model enabled. You can recognize which pages were enabled by checking to see if they contain the following lines. If the following lines do exist, you need to delete them. Delete these lines from the top of the ASP page:
   

   
         <!--METADATA TYPE="EditorGenerated" startspan <COMMENT>
         Visual InterDev Scripting Object Model - Page Header
         Do not modify between these meta data tags
         </COMMENT> -->
         <!--#include file="_ScriptLibrary/pm.asp"-->
         <% if StartPageProcessing() Then Response.End() %>
         <FORM name=thisForm METHOD=post>
         <!--METADATA TYPE="EditorGenerated" endspan--> 

   Delete these lines from the bottom of the ASP page:
   

   
         <!--METADATA TYPE="EditorGenerated" startspan <COMMENT>
         Visual InterDev Scripting Object Model - Page Footer
         Do not modify between these meta data tags
         </COMMENT> -->
         <% EndPageProcessing() %>
         </FORM>
         <!--METADATA TYPE="EditorGenerated" endspan--> 




5. After deleting the lines, right-click on the editor and choose Properties. Under the ASP settings, select the option Enable the scripting object model. Choose OK to close the dialog box and then save the file.

Remote Machine Debugging Server Component Must Be Installed with Windows NT Option Pack

Installation Problems with the Visual InterDev RAD Remote Deployment Support Server Component

1. On the Windows Start menu, choose Settings, and then Control Panel.



2. Double-click Add/Remove Programs.



3. From the list of software on the Install/Uninstall tab, select Windows NT 4.0 Option Pack.



4. Click Add/Remove to launch the Windows NT 4.0 Option Pack Setup.



5. In the Option Pack Setup, click Add/Remove when prompted. This displays a list of the Option Pack components.



6. Check the Visual InterDev RAD Remote Deployment Support option.



7. Click Next and continue with the Option Pack Setup.



8. Then, to correct the problem for existing projects, copy fp30reg.dll from:
   

   
         \Program Files\Microsoft FrontPage\version
         3.0\isapi\_vti_bin\_vti_aut" 

   
   to the master server at:
   

   
         "\inetpub\wwwroot\[projectname]\_vti_bin\_vti_aut" 

Known Issues: Product Related

Source Control Does Not Support File Names Containing Semi-Colons

Ignore Events in the Script Outline View for FRAME, IFRAME, FRAMESET, OPTION

Class Names Containing Underscores Are Not Supported

The Editor Does Not Support "<script>" or "</script>" Within JavaScript or VBScript Comments

Visual InterDev Does Not Support The ActiveMovie Control

When Working Offline and Editing in Design view, Relative URLs of Image Files Must Be Edited Manually

• Add the image in Source View.



• Add the image in Design view and specify an absolute URL in the Picture



• Source option of the Insert Image dialog box.



• Add the image in Design view and then edit the URL manually in Source view.

Visual Interdev Does Not Support Hierarchical Recordsets

Changes to Client Script Debugging in ASP Pages

3.  Under Server script, make sure that the Automatically enable ASP
    server- side script debugging on launch option is checked. 

5.  If debugging for client script in ASP pages has not been enabled as
    described above, Visual InterDev displays a message prompting you to
    enable debugging for ASP pages. Your options are:

    -Choose Yes if you are working with an ASP page and want Visual
    InterDev to automatically enable debugging.
    -Choose No if you if you are working with an HTM page and will not be
    navigating to an ASP page during your debugger session. 

Browsing "User Notification" Sample Using Netscape

1. Open the Microsoft Management Console on your Web server. From the Windows Start menu, select Programs, Windows NT 4.0 Option Pack, Internet Information Server, and then Internet Service Manager.



2. In the Gallery Web site, right-click the UserNote folder and choose Properties.



3. On the Directory Security tab, click the Edit button under Anonymous Access and Authentication Control.



4. In the Authentication Methods dialog box, make sure that Basic Authentication and Windows NT Challenge/Response are selected and that Allow Anonymous Access is not selected.



5. Click OK to close the dialog boxes.

Issue Concerning Window_Onload Event Not Firing

"[FrontPage vinavbar component]" Appears when Browsing a Page

• If the directory does exist, recalculate the links on the server:
  

  
     Run Fpsrvadm.exe on the server. Fpsrvadm.exe is typically found in
     "\Program Files\Microsoft FrontPage\version3.0\bin".
     When prompted to "Please enter command," select option #8, "recalculate
     links."
     When prompted to "Enter Web name," press ENTER. Do not type a Web name.
     This ensures that links are recalculated for all Webs recursively from
     the root Web. 




• If the directory does not exist, reinstall the FrontPage Server Extensions from the installation compact disc by running FP98ext\setup.exe. After they are installed, recalculate the links.

Difference in CSS Implementation Between Netscape and Internet Explorer

Use Server-Level Default Document Properties Only

Known Issues: Visual Component Manager

"Related Files Tab (Component Properties Dialog Box)" Topic Incorrect

Removing Repository 1.0 Registry Keys

• HKEY_LOCAL_MACHINE\Software\Microsoft\Repository\CacheMaxAnnProps



• HKEY_LOCAL_MACHINE\Software\Microsoft\Repository\CacheMaxObjects



• HKEY_LOCAL_MACHINE\Software\Microsoft\Repository\ CacheRelshipMaxCollections



• HKEY_LOCAL_MACHINE\Software\Microsoft\Repository\CacheRelshipMaxRows



• HKEY_LOCAL_MACHINE\Software\Microsoft\Repository\MaxRowCacheAge

Adding Repository Tables to an Existing .mdb File

Keywords : kbreadme kbExtension kbFrontPage kbServer kbVisID600 kbGrpASP
Version : WINDOWS:6.0
Platform : WINDOWS
Issue type : kbinfo