If you are upgrading to a new version of FileUpEE, remove the old version before installing the new version.
To create 3-tier upload and 3-tier download applications, you must install FileUpEE on both the web server and the file server. |
To run the automatic installer, double-click FileUpEE.exe, and follow the InstallShield instructions.
During installation you will be asked if the machine on which you are installing is a web server or a file server. If you are installing on a development machine that functions as both a web server and a file server, select "Web server."
To install FileUpEE the first time, run the automatic installer. Once InstallShield has unpacked the dll files that contain FileUpEE, you can re-install FileUpEE manually (if, for example, you are moving FileUpEE to a different server). Even when working in .NET, the COM .dlls must be registered.
To add the FileUpEE assemblies to your application:
The files you include in the bin directory must have the same version numbers as the files you registered to your server, either manually or using the automatic installer. Please note that FileUpEEModule.dll does not need to be registered, but must simply be added to the application's bin directory. |
Create a text file containing the contents of the example web.config file and save it as web.config. Make sure that the version number for the FileUpEeModule in the web.config file matches the version number of the FileUpEeModule.dll that you add to your application. Save web.config at the top level of your application.
The FileUpEEModule can be configured using the Application Keys in the application's web.config file. An explanation of the functions of each FileUpEEModule Application key can be found on this page: FileUpEEModule Application Settings
The <httpRuntime> node is not necessary in the web.config for the
FileUpEEModule to work. In order to allow large uploads, however, the executionTimeout
and maxRequestLength settings must be set appropriately. This will override the default
settings from the machine.config file. |
SoftArtisans strongly recommends using the HttpModule with all uploads in ASP.NET. The HttpModule is an interceptor that resolves memory utilization and disk caching performance issues in ASP.NET uploads. Though uploads can be performed without the HttpModule, there is a severe performance penalty with any large upload that does not use the HttpModule. Other benefits include server-side progress indication, increased speed due to reduced buffer size, and three-tier upload capability.
To install the FileUpEE HttpModule to your ASP.NET application, follow the instructions on the HttpModule installation page.
The FileUpEE assemblies - FileUpEE.dll, MimeClient.dll, FileUpEEModule.dll and FileUpEEProgress.dll - can be made accessible either globally or at the application level. If you would like the same .NET assemblies to be available to all applications, install the dll files in the Global Assembly Cache (GAC):
SoftArtisans recommends registering FielUpEE on the application level. |
The files you add to the GAC must have the same version numbers as the files registered to your server either manually or through the automatic installer. |
<add assembly="FileUpEE, Version=x.x.x.x, Culture=neutral, PublicKeyToken=f593502af6ee46ae"/>
<add assembly="MimeClient, Version=x.x.x.x, Culture=neutral, PublicKeyToken=f593502af6ee46ae"/>
<add assembly="FileUpEEProgress, Version=x.x.x.x, Culture=neutral, PublicKeyToken=f593502af6ee46ae"/>
<add assembly="FileUpEEModule, Version=x.x.x.x, Culture=neutral, PublicKeyToken=f593502af6ee46ae"/>
The version attribute of the add assembly node must correspond
exactly to the version of the assembly (dll file) added to the GAC. If you
add a new version of FileUpEE to the GAC using the gacutil command, update
the dll version attributes in machine.config. To get the exact version
of the dll file, right-click the dll and select the Properties tab. |
The FileUpEE assemblies that you add to your ASP.NET application must be the same DLL files that you registered to the GAC. |