Applications using the OpenEdge GUI for .NET require an appropriate version of the .NET Framework to run. An end user cannot start an OpenEdge GUI application without having an appropriate version of .NET installed. When you use WebClient to deploy one of these applications, your deployment must accommodate this requirement.

Note: Because users without Administrator privileges cannot install the .NET framework, you should consider this requirement carefully if your WebClient application supports personal installations.

You can address this requirement in the following ways:

  • Include the OpenEdge-certified version of the .NET Framework in your WebClient deployment through the IntelliStream System Tasks Definition dialog:


    This option packages a .NET Framework installer in the initial WebClient install. The WebClient Initializer checks the end-user's machine for either that version of the .NET Framework or a later version. If one is found, it aborts the install. This result enables both Administrator and personal installations to continue.

    Otherwise, it launches the .NET Framework installer. An end-user with Administrator privileges must accept the Microsoft EULA and complete the .NET Framework installation to continue installing your application. However, the framework installer fails for a non-Administrator, and the WebClient Initializer displays an error and aborts the personal installation.

  • Include a user-defined version of the .NET Framework in your WebClient deployment through the IntelliStream System Tasks Definition dialog. This option packages a .NET Framework installer that you supply in the initial WebClient install. Unlike with the OpenEdge-certified version, the WebClient Initializer does not check the end-user's machine for an existing .NET Framework. The WebClient Initializer always launches the user-defined .NET Framework installer. An end-user with Administrator privileges must accept the Microsoft EULA and complete the .NET Framework installation. However, the framework installer fails for a non-Administrator, and the WebClient Initializer displays an error and aborts the personal installation.

    For more information on appropriate versions of the .NET Framework, see the chapter on maintaining user environments in OpenEdge Deployment: Managing ABL Applications.

    CAUTION:

    Some .NET Framework installers might uninstall existing versions of the framework. You should verify what a particular installer does before including it in your WebClient deployment.

  • Do not include a .NET Framework installer in your WebClient deployment. This option leaves it to the end users to ensure that an appropriate version of the .NET Framework is available on their machines before they install your application.

Because WebClient cannot determine what other applications might require the framework, uninstalling WebClient or your WebClient application does not uninstall the .NET Framework.