HOWTO: Visual InterDev 6.0 Installation Tips

ID: Q243898


The information in this article applies to:
  • Microsoft Visual InterDev, version 6.0


SUMMARY

The installation procedure for Visual InterDev can vary greatly depending on your operating system, the products already installed on the target computer and situational needs. All installation scenarios are not covered in this article. These tips are designed to help you make general Visual InterDev installation decisions and will guide you through typical installations. For more assistance getting Visual InterDev installed, please contact Microsoft Technical Support.


MORE INFORMATION

General Visual InterDev 6.0 Installation Notes

  • If you are installing Visual InterDev 6.0 to a computer that has Visual InterDev 1.0 installed, it is recommended that you uninstall version 1.0 before installing version 6.0.


  • If you already have other Visual Studio components installed prior to installing Visual InterDev, you should start the Visual InterDev installation by going to START, SETTINGS, CONTROL PANEL, ADD/REMOVE PROGRAMS, MICROSOFT VISUAL STUDIO [product version], ADD/REMOVE.


  • Some of the Visual InterDev server components are operating system specific. It is important that the user install only the components that are specific to their operating system. In general, the user should install only the server components that are needed for their specific development needs.


  • If you already have the Windows NT Option Pack installed, you will need to uninstall it prior to installing any of the Visual InterDev Server components. If the Windows NT Option Pack is already installed and you try to make the necessary selections during the installation, you will get an error message stating that the Windows NT Option Pack is already installed and you cannot make changes. If you initially installed the Windows NT Option Pack using one of the CD-ROMs from an MSDN subscription, you must uninstall it through Add/Remove programs using that same CD-ROM. The Visual InterDev Server components installation uses the BackOffice installation script, which is different from the installation done from the MSDN subscription CD-ROM. The Visual InterDev installation script may not properly recognize the Windows NT Option Pack if it has been installed by other means. If you have any questions about the components that will be removed when you remove the Windows NT Option Pack, please contact Microsoft Technical Support for assistance.


  • If you have Office 2000 installed on your computer, the 2000 FrontPage Server Extensions may have been installed as well, even if you did not install FrontPage 2000. Visual InterDev Web server connections use the FrontPage Server Extensions. Visual InterDev servers do not recognize the 2000 FrontPage Server Extensions because they were released prior to the 2000 products. Therefore, you should uninstall the 2000 FrontPage Server Extensions prior to installing Visual InterDev. If you see the 2000 FrontPage Server Extensions listed under Add/Remove Programs, you can uninstall it there, or if you're not sure, you can uninstall all Office 2000 components and the Server Extensions will be removed. After Visual InterDev is installed and configured, you can re-install the 2000 FrontPage Server Extensions and/or Office 2000 and the products will function properly together. This information does not apply if your operating system is Windows 2000 Professional or Server.


  • If you install both Visual InterDev and Visual J++, you will have an additional set of tools in your toolbox called WFC Controls. Even if you're not planning to develop in Visual J++, you may want to install it so that you have access to this additional set of tools.


  • If your operating system is Windows 2000 Professional or Server and you wish to have a local server, install Internet Information Server from the Add/Remove Windows Components utility prior to installing Visual InterDev.


Visual InterDev Setup Configurations:

Scenario 1: Product Installation Only

You will be developing on your local computer, but copying your web project to a remote server for viewing or execution. The remote server will be either Internet Information Server (IIS) or Personal Web Server (PWS).

To complete this installation:
  1. Insert installation compact disc #1 into your computer.


  2. Setup.exe automatically runs the Installation Wizard. If the Setup program doesn't AutoRun, you can start the installation by double-clicking Setup.exe, located on install CD1.The wizard steps you through the installation process. You may complete either a typical or custom install.


  3. NOTE: Depending on your selections and your current configuration, the wizard will prompt you to install different required components and to restart Windows one or more times during the installation process. After each restart, the wizard automatically returns to the proper step.

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


Scenario 2: Product Installation With Some Server Components on Windows NT Workstation

You will be developing on your local computer and need the ability to have Active Server pages previewing on your local computer.

To complete this installation:

  1. Insert installation CD-ROM #1 into your computer.


  2. Setup.exe automatically runs the Installation Wizard. If the Setup program doesn't AutoRun, you can start the installation by double-clicking Setup.exe, located on install CD1. The wizard steps you through the installation process. You may complete either a typical or custom install.


  3. NOTE: Depending on your selections and your current configuration, the wizard will prompt you to install different required components and to restart Windows one or more times during the installation process. After each restart, the wizard automatically returns to the proper step.

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


  5. After MSDN is installed, you arrive at the Server Setups screen. Select Launch BackOffice Installation Wizard and click Install.


  6. Select Custom and click Next.


  7. Verify the disk space requirements and click Next.


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

    NOTE: If your operating system is Windows 2000 Professional, you will not see the following components listed. If you have not already installed Internet Information Server via Add/Remove Windows Components, you need to exit the setup and complete that step prior to continuing with the Visual InterDev setup. When you run the Visual InterDev setup again, you will resume at step 4 above. If you have already installed Internet Information Server, you can proceed to step 8 now.


  9. Expand the Windows NT Option Pack node and select:


  10. FrontPage Server Extensions
    Microsoft Data Access Components
    Microsoft Management Console
    NT Option Pack Common Files
    Personal Web Server (PWS)
    Transaction Server


  11. Deselect the remaining components. As you deselect 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 true server.


  12. Continue with the remaining steps of the wizard.



Scenario 3: Product Installation With Some Server Components on Windows NT Server

You will be developing on your local computer and need the ability to have Active Server pages previewing on your local computer.

To complete this installation:

  1. Insert installation CD-ROM #1 into your computer.


  2. Setup.exe automatically runs the Installation Wizard. If the Setup program doesn't AutoRun, you can start the installation by double-clicking Setup.exe, located on install CD1.The wizard steps you through the installation process. You may complete either a typical or custom install.


  3. NOTE: Depending on your selections and your current configuration, the wizard will prompt you to install different required components and to restart Windows one or more times during the installation process. After each restart, the wizard automatically returns to the proper step.

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


  5. After MSDN is installed, you arrive at the Server Setups screen. Select Launch BackOffice Installation Wizard and click Install.


  6. Select Custom and click Next.


  7. Verify the disk space requirements and click Next.


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


  9. NOTE: If your operating system is Windows 2000 Server, you will not see the following components listed. If you have not already installed Internet Information Server via Add/Remove Windows Components, you need to exit the setup and complete that step prior to continuing with the Visual InterDev setup. When you run the Visual InterDev setup again, you will resume at step 4 above. If you have already installed Internet Information Server, you can proceed to step 8 now.

  10. Expand the Windows NT Option Pack node and select:


  11. Front Page Server Extensions
    Microsoft Data Access Components
    Internet Information Server
    Microsoft Management Console
    NT Option Pack Common Files
    Transaction Server


  12. Deselect the remaining components. As you deselect 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 true server.


  13. Continue with the remaining steps of the wizard.



Scenario 4: Product Installation With Some Server Components on Windows 9x

You will be developing on your local computer and need the ability to have Active Server pages previewing on your local computer.

To complete this installation:

  1. Insert installation CD-ROM #1 into your computer.


  2. Setup.exe automatically runs the Installation Wizard. If the Setup program doesn't AutoRun, you can start the installation by double-clicking Setup.exe, located on install CD1.The wizard steps you through the installation process. You may complete either a typical or custom install.


  3. NOTE: Depending on your selections and your current configuration, the wizard will prompt you to install different required components and to restart Windows one or more times during the installation process. After each restart, the wizard automatically returns to the proper step.

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


  5. After MSDN is installed, you arrive at the Server Setups screen.


  6. Select NT Option Pack (for Windows 9x) 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 (If you have a later version installed, it will not be replaced during this installation.)
      Personal Web Server (PWS)
      Transaction Server

    • Deselect the remaining components. As you deselect 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 true server.


    • Continue with the remaining steps of the Personal Web Server Setup.


    After this step is complete, you should see the Personal Web Server (PWS) icon appear in the system tray on your task bar and it will start automatically.

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


  8. Continue with the remaining steps of the wizard.



Scenario 5: Product Installation With Server Components on Windows NT

You will be developing on your local computer and will act as a Visual InterDev server for other developers over a network.

To complete this installation:

  1. Insert installation CD-ROM #1 into your computer.


  2. Setup.exe automatically runs the Installation Wizard. If the Setup program doesn't AutoRun, you can start the installation by double-clicking setup.exe, located on install CD1.The wizard steps you through the installation process. You may complete either a typical or custom install.


  3. NOTE: Depending on your selections and your current configuration, the wizard will prompt you to install different required components and to restart Windows one or more times during the installation process. After each restart, the wizard automatically returns to the proper step.

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


  5. After MSDN is installed, you arrive at the Server Setups screen. Select Launch BackOffice Installation Wizard and click Install.


  6. Select the Custom option and click Next.


  7. Select the following options:


  8. Windows NT Option Pack 4.0
    MS Data Access Components
    Remote Machine Debugging
    FrontPage Server Extensions
    Visual InterDev Server


  9. 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.


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


  11. 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. NOTE:If you have NT Service Pack 4 installed on the computer, this patch is not necessary.


    • Run \IIS\WinNT\ASP2FIXI.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.

    • Restart when prompted.



Scenario 6: Product Installation With Server Components on Windows 9x

You will be developing on your local computer and will act as a Visual InterDev server for other developers over a network.

To complete this installation:

  1. Insert installation compact CD-ROM #1 into your computer.


  2. Setup.exe automatically runs the Installation Wizard. If the Setup program doesn't AutoRun, you can start the installation by double-clicking Setup.exe, located on install CD1.The wizard steps you through the installation process. You may complete either a typical or custom install.


  3. NOTE: Depending on your selections and your current configuration, the wizard will prompt you to install different required components and to restart Windows one or more times during the installation process. After each restart, the wizard automatically returns to the proper step.

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


  5. When the Installation Wizard arrives at the Server Setups screen, you will be prompted to make a selection from the Server Components list. Install each of the components as instructed below.


  6. NOTE: In order to assure that your server is set up correctly, you must install the server components in the order that they are listed on the Server Setups screen.

  7. Select NT Option Pack (for Windows 9x) and click Install. This launches the Microsoft Personal Web Server Setup.


    1. When prompted to select Minimum, Typical, or Custom, select Typical.


    2. Continue with the remaining steps of the Personal Web Server Setup.


    After this step is complete, you should see the Personal Web Server (PWS) icon appear in the system tray on your task bar and it will start automatically.

  8. Select FrontPage 98 Server Extensions and click Install.


  9. Select Data Access Components 2.0 and click Install.


  10. Select Visual InterDev Server Components and click Install.


  11. Click Finish to complete the server components installation process.


  12. 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.


    1. First, stop the Web server by right-clicking on the icon on the task bar and selecting "Stop Service"


    2. In the \windows\system\inetsrv directory, rename Asp.dll to Asp.old.


    3. Copy \IIS\Win9x\Asp.dll from the installation disc to your \windows\system\inetsrv directory.


    4. 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.

    5. Restart the Web server by right clicking on the icon on the task bar and selecting "Start Service"



Scenario 7: Server Components on Windows NT

You will not be developing on your local computer, but will act as a Visual InterDev server for other developers over a network.

To complete this installation:

  1. Insert installation compact CD-ROM #1 into your computer.


  2. Navigate to the Server Setups screen. Select Launch BackOffice Installation Wizard and click Install.


  3. Select the Custom option and click Next.


  4. Select the following options:


  5. Windows NT Option Pack 4.0
    MS Data Access Components
    Remote Machine Debugging
    FrontPage Server Extensions
    Visual InterDev Server


  6. 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.


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


  8. 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. NOTE: If you have NT Service Pack 4 installed on the computer, this patch is not necessary.


    1. Run \IIS\WinNT\ASP2FIXI.EXE from the installation disc.


    2. 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.

    3. Restart when prompted.



Scenario 8: Server Components on Windows 9x

You will not be developing on your local computer, but will act as a Visual InterDev server for other developers over a network.

To complete this installation:

  1. Insert installation compact CD-ROM #1 into your computer.


  2. Under Add/Remove options, choose Server Applications and Tools (Add only) and then click Next.


  3. At the Server Setups screen, you will be prompted to make a selection from the Server Components list. Install each of the components as instructed below.


  4. NOTE: In order to assure that your server is set up correctly, you must install the server components in the order that they are listed on the Server Setups screen.

  5. Select NT Option Pack (for Windows 9x) and click Install. This launches the Microsoft Personal Web Server Setup.


    1. When prompted to select Minimum, Typical, or Custom, select Typical.


    2. Continue with the remaining steps of the Personal Web Server Setup.


    After this step is complete, you should see the Personal Web Server (PWS) icon appear in the system tray on your task bar and it will start automatically.

  6. Select FrontPage 98 Server Extensions and click Install.


  7. Select Data Access Components 2.0 and click Install.


  8. Select Visual InterDev Server Components and click Install.


  9. Click Finish to complete the server components installation process.


  10. 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.


    1. First, stop the Web server by right clicking on the icon on the task bar and selecting "Stop Service"


    2. In the \windows\system\inetsrv directory, rename Asp.dll to Asp.old.


    3. Copy \IIS\Win9x\Asp.dll from the installation disc to your \windows\system\inetsrv directory.


    4. 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.

    5. Restart the Web server by right clicking on the icon on the task bar and selecting "Start Service"



Scenario 9: Production Server Installation for Windows NT

To ensure that your Web application will run properly on a production server installed with Windows NT, you must install some of the Visual Studio server components on that computer.

NOTE: Windows 95 and Windows 98 are not recommended as production server platforms for running Visual InterDev 6.0 applications. The components needed on a production server are:

  • 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)


Furthermore, if you intend to allow applications to be deployed to the production server, you may want to install the FrontPage Server Extensions or the Visual Studio Posting Acceptor.

Perform the following steps to install the server components on a Windows NT production server.

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


  2. Select the Custom option and click Next.


  3. Select the following options:


  4. Windows NT Option Pack 4.0
    MS Data Access Components
    Front Page Server Extensions - Optional
    Posting Acceptor (2.0) - Optional
    Visual InterDev Server

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



Configuring Visual InterDev on Windows NT Computers After the Installation

If you have installed Visual InterDev on an NT computer in a scenario where you will be developing on your local computer and have at least some of the server components installed, you will need to configure the product before you begin the development process.

To complete the configuration:

  1. Launch the FrontPage Server Administrator:


    • For computers running Windows NT, click the Start menu, click point to Programs, and click Windows NT 4.0 Option Pack, Microsoft Internet Information Server, or FrontPage Server Administrator. Or you can launch the FrontPage Server Administrator by locating Fpsrvwin.exe and double-clicking on this file.


    • For computers running Windows 95 or Windows 98, click the Start menu, point to Programs, and click Microsoft Personal Web Server, or FrontPage Server Administrator.


  2. Click the Install button, select Microsoft Internet Information Server from the drop-down box and accept the default settings to complete the installation. This process will install the FrontPage Server Extensions on the Microsoft Internet Information Server.


  3. NOTE: If you installed Visual InterDev on a 9x machine, your Personal Web Server (PWS) should have been configured automatically during the installation process. If you do not have a PWS icon in the system tray of your task bar, you can start the PWS by locating and double-clicking on pws.exe. The default path to this file is c:\Windows\System\Inetsrv\pws.exe. If you are not able to connect to the PWS via Visual InterDev, please contact Microsoft Technical Support for assistance.

Testing Visual InterDev functionality

Once you have completed the Visual InterDev installation and the installation of FrontPage Server Extensions on the Microsoft Internet Information Server (if needed for your scenario), you will be ready to test the functionality of Visual InterDev.

To test the functionality:

  1. Launch the Visual InterDev application. NOTE: If you have also installed Visual J++, you will see both products displayed on the splash screen and in other areas throughout Visual InterDev because they share the Integrated Development Environment (IDE).


  2. In the New Project window, verify that Visual InterDev Projects is highlighted.


  3. Select New Web Project.


  4. Designate the project Name and Location and then click Open.


  5. The Web Project Wizard will be launched and you will be at step 1 of 4 where you will need to specify a server and mode.


    1. In the drop-down box below "What server do you want to use?" type in your computer name. If you do not know your computer name, you can determine this by going to START, SETTINGS, CONTROL PANEL, NETWORK, under the IDENTIFICATION tab, you will find your Computer Name. On Windows 2000 computers, go to START, SETTINGS, CONTROL PANEL, NETWORK and DIAL-UP CONNECTIONS, NETWORK IDENTIFICATION TAB.


    2. Under "What mode do you want to work in?" select:


      • Master mode if you want changes made to files to be saved to both the local files on your workstation Web application and the master files on the master Web server.


      • Local mode if you want changes made to files to be saved to your workstation's copy of the file residing in the local Web application and not to the master Web application. The master Web application must be updated explicitly by releasing the working copy or synchronizing the project.


    3. Click Next. You will see a message stating "Contacting Web server".


    4. For additional information on the error message, 'Unable to contact web server', click the article number below to view the article in the Microsoft Knowledge Base:
      Q243898 PRB: Troubleshooting 'Unable to Contact Web Server' in Visual InterDev
      NOTE: If the wizard progresses past this screen to step 2 of 4, you know that the web server has been properly configured. If not, you will receive a message stating that it was "Unable to contact web server http://Computer Name". Another possible reason that you might receive this message is that the web server has been stopped and should be restarted or that you do not have privileges to connect to the web server. On Windows NT 4 Server computers, you can check the server status under Services in the Control Panel. On Windows 2000 Server computers, Services is located under Administrative Tools. On Windows NT 4 Workstation and Windows 9x computers, check to see if the PWS icon in the system tray on your task bar has a red mark through it. If so, right-click on the icon and choose "Start Service".

    5. Continue with the remaining steps of the wizard. When you select Finish, you will see a message stating "Creating Project File" and "Copying Script Library". When the process in complete, your Visual InterDev Integrated Development Environment (IDE) will be open with your Toolbox and Project Explorer visible.


    6. Click on any file listed in the Project Explorer.


    7. From the menu at the top of the screen, select Project, Add Item, Site Diagram, give the diagram a name and then click Open. An Open Web dialog box will appear and then the new Site Diagram page will open displaying the default, Home (default.htm).


    8. Save the project and notice that Default.htm now displays in the Project Explorer.


    9. Double-click on Default.htm and it will open.


    10. Type a message on the page and then Save the project again.


    11. Right-click on Default.htm in the Project Explorer window and select View in Browser. Your browser window should open with your new creation displayed


Additional query words: KbSetup KBVS600

Keywords :
Version : WINDOWS:6.0
Platform : WINDOWS
Issue type : kbhowto


Last Reviewed: January 26, 2000
© 2000 Microsoft Corporation. All rights reserved. Terms of Use.