WebHelp Plus and HTML5 Server-Based output requirements for Flare V9+

Article #:OUTWP1004F

Product: Flare

Version:9

Full Description:

Server-Based outputs from Flare V9+ is now designed to work with a .NET 4.0 website and will require the Application Pool to be upgraded to use .NET Framework Version 4.0. The following updates on the server will need to be done to get the output to work correctly after upgrading to Flare V9+.

Solution:

  1. Install Microsoft .NET Framework 4.0 if it was not previously installed on the computer.
  2. ASP.NET V4.0 will need to be activated.

    • In Windows, click Start>Run. The Run dialog opens.
    • In the Open field, copy and paste one of the following into the field, depending on whether the server is a 32-bit or 64-bit system:
    • 32-bit

      C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis -i

      64-bit

      C:\WINDOWS\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis -i

    • Click OK.
    • A window opens, displaying the installation progress of ASP.NET. The window will close automatically when the installation finishes.
  3. Open IIS and expand the site to locate the published output
  4. Right-Click on the 'Service' Folder and select Manage Application> Advanced Settings to determine the name of the Application Pool being used for the Service.

  5. Navigate to the Application Pools Section of IIS

  6. In the list of Application Pools, locate and select the one listed from step 4
  7. Right-Click on the selected Application Pool and select "Basic Properties"
  8. In the drop-down menu for the .NET Framework Version, switch to .NET Framework V4

  9. Click OK and save changes.
  10. Restart the Application Pools
  11. Return to the published output folder and open the Service/Console.ConfigureSearch folder
  12. Locate and launch ConfigureSearch.exe. A small command line open and close.
  13. Test the functionality of the output by refreshing the site and reloading the output on a browser

Note: If the project has other WebHelp Plus or HTML5 Server-Based targets which are merged at run-time, the merged outputs will also need to be properly enabled on the IIS Server. The merged outputs will be published to a "Subsystems" folder inside of the main project's output folder.

Attribution:

Last updated:

March 8, 2013

Author:

Lori Okamoto

Contributions by:

MadCap QA, MadCap Documentation