Before performing the automatic installation steps, please read the section Before You Install. This section will help you plan your responses to questions posed by the installer.

To run the automatic installation, double-click FileUp.exe, and follow the InstallShield instructions.

The auto-installer will register the appropriate dlls in COM, as described in the "Manual Installation" section below. It will also set up samples in IIS. After running the auto-installer, please proceed to the Tailoring Your Installation chapter.

Also, the auto-installer does not make FileUp available to .NET. You must follow additional instructions to make FileUp availabe to the .NET framework on an application or global level. Please see: Making FileUp Available to .NET Applications.

To install FileUp the first time, run the automatic installation. Once InstallShield has unpacked the dll files that contain FileUp, you can re-install FileUp manually (if, for example, you are moving FileUp to a different server).

FileUp Specific dlls:

FileUp includes two sets of dll files in the folders COM and DotNet. The dlls in COM are only for direct use in ASP. The dlls in DotNet provide an interop assembly for use in ASP.NET and should not be installed on a server that does not have the .NET Framework. Most of FileUp's ASP.NET .dll files are not pure .NET assemblies; you must register the associated COM DLLs using regsvr32 before you can use them in .NET.

The following table lists all of the .dll files included with FileUp that require COM registration. To use an optional file, register the file with regsvr32(as explained above).

The following dll is included with FileUp and as a pure .NET assembly should notbe registered in COM. It should instead be copied to your webserver for use in the configuration step "Making FileUp Accessible to .NET applications"

To register the FileUp specific dlls in COM:

1. Open a command prompt window and move to the directory FileUp\COM.
   For example, enter cd Program Files\SoftArtisans\FileUp\COM.
   
   
2. Enter regsvr32 SAFileUp.dll. A dialog box will inform you that SAFileUp.dll registered successfully; click OK.
   
   
3. (Optional). To provide support for Progress Indication;
   Enter regsvr32 SAPrgres.dll. A dialog box will inform you that SAPrgres.dll registered successfully; click OK.
   
   
4. (Optional). To provide support for performance monitoring;
   Enter regsvr32 SAFupmon.dll. A dialog box will inform you that SAPrgres.dll registered successfully; click OK.
   Note: This dll does not provide any functionality that would be included in your application, but is only used through the Windows Performance Monitor. Therefore, there will be no further information on the dll regarding making it available to your application in .NET.
   
   
5. Enter iisreset to reset IIS.
   
   

The following dlls are distributed with FileUp as accessory components. These include the products File Manager, Archive and SMTPmail. These are COM components and do not provide any built-in .NET support. To be used in .NET, they must first be registered in COM and then an interop assembly must be generated with a tool such as Visual Studio.NET or the Type Library Importer (Tlbimp.exe) provided by the .NET Framework SDK. Each of these products can also be purchased separately and therefore have their own documentation set. The API documentation for each of these products is also included in the Programmers Reference section of this documentation

After registering the appropriate dlls, at a minimum, you will need to create the FileUpTempDir registry key to specify the caching directory for the HttpModule. This key, as well as all of the optional keys are listed in Tailoring Your Installation: FileUp Registry Keys .