Home     Products      Support      Corporate     Sign In 
Support Knowledge Base, Article 757
Product
FileUp
Version
Version 4
Title
Windows 2003 and IIS 6 support for version 4.x of FileUp
Problem
IIS 6 has a new processing model. This article explains what compatibility issues to look for and how to make decisions about migrating or developing your FileUp application for IIS 6.
Solution

This article is intended to explain your IIS 6 support options for version 4 of FileUp. FileUp version 4 only provides partial support for IIS 6. For full IIS 6 support, FileUp should be upgraded to version 5*.

If you intend to run your FileUp application on a Windows 2003/ IIS 6 server you will need to examine your application needs before migrating or developing your application.

IIS 6 compatibility

The only compatibility issue with FileUp and IIS 6 is the use of FileUp's ISAPI filter. The ISAPI filter was designed for the IIS 5 processing model, and is not appropriate for IIS 6's native processing model, which does not support this type of "Read Raw Data" ISAPI-level filter. This means that if you want to use the FileUp ISAPI filter, you will need to run your entire IIS 6 webserver in IIS 5 Isolation mode.

How do you know if you should be using the ISAPI filter?

The ISAPI filter was designed to circumvent ASP.NET's behavior of forcing uploads to be cached to memory. Caching an upload to memory can be an inefficient use of server resources, compromising performance on heavily used sites. The ISAPI filter allows FileUp to cache the upload to disk, as was traditionally supported in ASP.

  • If your application is an ASP application, in most cases, you will not need to use the ISAPI filter.
  • If you are running a .NET application on IIS 5 with version 4 of FileUp, then the ISAPI filter is the best solution for improving memory resource utilization.
  • If you are moving your application from IIS 5 to IIS 6, you will want to check to see if you are already using the FileUp ISAPI filter. This can be done in two steps. First, check your scripts to see if they are marked to be processed by the filter, and then confirm that the filter is installed. Scripts are marked to be processed by the filter by changing the filename extension to ".upl" or ".uplx". The ISAPI filter gets installed in IIS at the machine level. For step by step instructions for how this is done, please see our online documentation both of these topics at: http://support.softartisans.com/docs/FileUpV4/prog_g_dotnet_largeuploads.htm#isapi
  • If you are running your .NET application on IIS 6 with the FileUp ISAPI filter, you will need to run your server in IIS 5 Isolation mode in order to use the filter.
  • If you are running your .NET application on IIS 6 and would like to have the functionality of ISAPI filter, but cannot run your server in IIS 5 Isolation Mode, then you will need to upgrade to version 5* of FileUp and use the HttpModule instead. FileUp version 5's HttpModule is designed to replace the ISAPI filter as it is designed for IIS 6's native processing model.
  • If FileUp's ISAPI filter conflicts with any other ISAPI level filters on your webserver, then you will want to upgrade to version 5* of FileUp and use the HttpModule instead.


*FileUp Version 5 is scheduled to be released in January 2004

Related Links:

More information on the ISAPI filter in FileUp version 4.
How do I set my IIS 6 server to run in IIS 5 Isolation Mode?
How do I uninstall the ISAPI filter?
How do I upgrade or purchase FileUp version 5?

Created : 12/17/2003 1:21:55 PM (last modified : 3/1/2004 2:14:22 PM)
Rate this article!
 
Comments