Application Server Solutions for Microsoft IIS and ASP.NET
       solutions   products   partners   company   support   downloads         store
ServletExec Self-Help: FAQ
Back to Search >  Back to Search Results

Faq ID 248
Product BlueDragon
Category Installation
Question I've installed BlueDragon.NET but it doesn't work properly. How can I verify it was installed properly?
Answer Perform the following steps to verify BlueDragon.NET was installed properly:
  1. For a single virtual directory install, verify the following DLLs were placed in the <installation directory>\bin directory: BlueDragon.dll, BlueDragon.Controls.dll, BlueDragon.Utils.dll and CFX.NET.dll. For all other installs, verify these DLLs were installed to the Global Assembly Cache (GAC). The GAC is located at <Windows directory>\assembly.

  2. For a single virtual directory install, verify a web.config file exists in the <installation directory> directory. This file must contain the following elements (NOTE: To make this FAQ easier to read, some attribute values are shown on multiple lines. When manually entering these elements, the attribute values must be placed on a single line.):
    • <section name="bluedragon"
               type="System.Configuration.NameValueSectionHandler,
                     System, Version=1.0.5000.0, Culture=neutral,
                     PublicKeyToken=b77a5c561934e089" />
      
    • <bluedragon>
        <add key="SINGLE_WEB_APP" value="TRUE"/>
      </bluedragon>
      
    • <add verb="*" path="*.cfc"
           type="NewAtlanta.BlueDragon.CfmHttpHandler,
                 BlueDragon, Version=6.2.0.0, Culture=neutral,
                 PublicKeyToken=7551335de9fc3c36"
           validate="false" />
      <add verb="*" path="*.cfml"
           type="NewAtlanta.BlueDragon.CfmHttpHandler,
                 BlueDragon, Version=6.2.0.0, Culture=neutral,
                 PublicKeyToken=7551335de9fc3c36"
           validate="false" />
      <add verb="*" path="*.cfm"
           type="NewAtlanta.BlueDragon.CfmHttpHandler,
                 BlueDragon, Version=6.2.0.0, Culture=neutral,
                 PublicKeyToken=7551335de9fc3c36"
           validate="false" />
       
    For all other installs, verify machine.config, which is lcoated at <Windows directory>\Microsoft.NET\Framework\<version>\CONFIG, contains the following elements (NOTE: To make this FAQ easier to read, some attribute values are shown on multiple lines. When manually entering these elements, the attribute values must be placed on a single line.):
    • <section name="bluedragon"
               type="System.Configuration.NameValueSectionHandler,
                     System, Version=1.0.5000.0, Culture=neutral,
                     PublicKeyToken=b77a5c561934e089" />
      
    • <bluedragon>
        <add key="BLUEDRAGON_DIRECTORY" value="<installation directory>"/>
      </bluedragon>
      
    • <add assembly="BlueDragon.Controls, Version=6.2.0.0, Culture=neutral,
                     PublicKeyToken=67fb241f107321af" />
      <add assembly="BlueDragon, Version=6.2.0.0, Culture=neutral,
                     PublicKeyToken=7551335de9fc3c36" />
      
    • <add verb="*" path="*.cfc"
           type="NewAtlanta.BlueDragon.CfmHttpHandler,
                 BlueDragon, Version=6.2.0.0, Culture=neutral,
                 PublicKeyToken=7551335de9fc3c36"
           validate="false" />
      <add verb="*" path="*.cfml"
           type="NewAtlanta.BlueDragon.CfmHttpHandler,
                 BlueDragon, Version=6.2.0.0, Culture=neutral,
                 PublicKeyToken=7551335de9fc3c36"
           validate="false" />
      <add verb="*" path="*.cfm"
           type="NewAtlanta.BlueDragon.CfmHttpHandler,
                 BlueDragon, Version=6.2.0.0, Culture=neutral,
                 PublicKeyToken=7551335de9fc3c36"
           validate="false" />
       
    If web.config or machine.config doesn't contain the proper elements then check <installation directory>\BlueDragonInstaller.log for error messages.

  3. For a single virtual directory install, verify a virtual directory was created in IIS that maps to the <installation directory>.

  4. For the web site or virtual directory you are having problems with, verify it is configured with extension mappings for .cfm, .cfml and .cfc that map to the aspnet_isapi.dll for the version of the .NET Framework you are using. These extension mappings must not have the setting "Check that file exists" enabled.



   
company media information terms of use privacy policy contact us