FileUp's progress indicator cannot show accurate progress in an ASP.NET environment if it is not used in conjunction with either the HttpModule or the ISAPI filter. This is because ASP.NET forces the upload to be cached to memory.

If the HttpModule or ISAPI filter is used in conjunction with FileUp, the upload will be intercepted and cached to disk. This allows for accurate display of the server-side progress of the upload. If you are running FileUp sample code, be certain that you are running samples that have a filename extension of "*.uplx". This filename extension marks the upload to be handled by either the HttpModule or the ISAPI filter, assuming that one or the other is properly installed on the web server.

For more detailed instructions and installation troubleshooting tips relating to this topic, please see:

• Using the Progress Indicator: http://support.softartisans.com/docs/FileUp/prog_g_progress.htm
  
  
• More on the HttpModule: http://support.softartisans.com/docs/FileUp/prog_g_LargeUploads_dotnet.htm
  
  
• Installation check list for the HttpModule: http://support.softartisans.com/kbview.aspx?ID=795
  
  
• Installation check list for the ISAPI filter:http://support.softartisans.com/docs/FileUp/install_dotnet.htm#isapi
  
  
• Setting Up Application Mappings so that the ISAPI filter or HttpModule will process your scripts: http://support.softartisans.com/docs/FileUp/install_dotnet.htm#uplx