Single File Deployment

Most of the time, all you need to do is to copy EO.Web.dll into your web application's bin folder. If you use a license file, also put the license file in the application's bin folder. However, additional steps may be needed under some circumstance.

JavaScript files

Unlike other products on the market, there is no JavaScript file to copy when deploying EO.Web Controls. The script files are built into EO.Web.dll and are rendered dynamically at runtime. A script file is typically rendered in the form of:

__eo_dp.aspx?id=404D1273-BF3C-4e99-A8DD-C781E4B0E17F

At runtime, EO.Web Controls are able to intercept and serve this Url as if it was a real script file.

EO.Web Controls can also generate physical script files at a specified location and render script files as links to that location. Using physical script files is recommended because it yields better performance.

In order to use physical script files, you must explicitly initialize EO.Web Runtime using one of the approaches described in the following section and specify a valid script location along with the initialization.

Multi-CPU server, server farm and partial-trust considerations

To properly serve the "virtual dynamic Url" (described above), EO.Web Controls runtime environment must be initialized. EO.Web Controls runtime environment is automatically initialized when the first EO.Web Control is rendered. However, on a multi-CPU server or a server farm environment, a "virtual dynamic Url" request generated by one server/process may go to another server/process on which the EO.Web Controls runtime environment is not initialized yet. In this case the dynamic Url request will fail.

Automatic initialization also requires reflection permission which is not granted if the server is configured as partial trust environment. Partial trust is enabled by setting the trust level in web.config or machine.config to a value rather than "Full", for example, the following line sets the trust level to "High":

<trust level="High" />

Usually this is set in machine.config by your web hoster and cannot be overriden by you in your local Web.config file.

To avoid these problems, copy eo_web.ashx from the installation folder to the root directory of your Web application.

Placing eo_web.ashx at a different location

If you use ASP.NET permission control and the root directory is not accessible by all pages, you may wish to consider placing eo_web.ashx at a different location that is accessible to all pages. In order to place the file at a different location, you need to:

• Put the file at the desired location;
• Add the following appSettings entry to info EO.Web Controls the location of the file:

  <appSettings>
      <add key="eo_HandlerLocation" value="~/some_where"></add>
  </appSettings>
  

Physical script files

You can also optionally specify a physical script file location in the config file by adding an appSettings entry:

<appSettings>
    <add key="eo_ScriptLocation" value="~/eo_script"></add>
</appSettings>

Note that the value specifies a directory that must be writable by your application.