In version 5.1.1 or higher of FileUpEE, since there have been no changes in the API it is not necessary to make any changes to your existing code. However, certain configuration changes are required.
Before running the new installer, first uninstall the old version of FileUpEE from Add/Remove Programs. To make sure there will be no lock on the dlls, it is recommended that you first reset IIS, then un-install the old version and then install the new version.
The most significant configuration change for version 5.1.1 or higher of FileUpEE is that the settings for the HttpModule are no longer in the registry, but rather in the web.config file of your ASP.NET application. This allows you to have different settings for different file transfer applications on the same machine. There is also one minor change required to global.asax in relation to a known issue in the .NET/COM Interop. When deploying the version 5.1.1 or higher into your FileUpEE application, make the following changes to web.config and global.asax:
If you have a 3-tier architecture, all the configuration changes listed above need to be made on both webserver and fileserver tiers.
- As seen in the attached sample web.config file (this file will be un-packed to “\SoftArtisans\FileUpEE\samples\web.config” with the installer of version 5.1.1 or higher), all the following key entries should be present in the <appSettings> section in your application's web.config file:
These are the configuration settings required by the new FileUpEeModule, and will result in an error if removed. For details about each key setting, see the comments in the attached sample web.config file.
* The TraceLogFile key entry is required only if tracing is turned on using the TraceLevelSwitch key in the <system.diagnostics><switches> section. Otherwise it can be omitted.
- Modify the settings as desired for your application.
- If you will use FileUpEE in .NET 2.0 applications, make sure to un-comment the <buildProviders> section as indicated in the attached sample web.config file.
- As seen in the attached sample global.asax code-behind files ("Global.asax.cs" for C# and "Global.asax.vb" for VB), add the AppDomainUnloadHandler event handler in your application's global.asax file. Then copy the code seen in the Application_Start handler of the sample to the Application_Start handler in your global.asax file.( A "Global.asax.cs" file with a similar code to the attached one will be un-packed to "\SoftArtisans\FileUpEE\samples\Global.asax.cs" with the installer of version 5.1.1 or higher)
Note: If you are using FileUpEE in ASP, there are no changes required at all.