• ActiveX upgrades from older versions of XFile to versions 2.5.1 or 2.5.2 did not complete properly due to the addition of the non-administrative installation option
  • The distributed XFile cab now only provides an administrative installation option. There is a separate per-user cab available by special request. 

• In Windows Vista and above clients with Internet Explorer 7 and above, implemented the ability to save files to any accessible directory while Internet Explorer is running in protected mode.

• Sending a regular GET request that doesn’t involve file download caused Internet Explorer to crash.
• During downloads, turning on debug logging in the XFRequest object caused the “Unknown Error Occurred” error. In version 2.5.1, the same bug caused Internet Explorer to crash.
• FileManager: FileManager’s "TextStream" object couldn’t properly read ANSI encoded text content and rendered it as question mark characters.

New Features:

• Fully supports non-administrative ActiveX installation in Internet Explorer 8 on platforms running Windows Vista and later(for reference see MSDN article: Non-Admin ActiveX Controls)
• Significantly improved performance of XFile ASP.NET samples using custom HTML client-side progress indicator

New Features:

• New method AddEncryptedRequestHttpHeader in XFileEE's XFRequest object to be used with FileUpEE's new Encryption class (see KB article: Session loss in ASP.NET 2.0 using XFileEE with FileUpEE)

Issues resolved:

• Addressed the possible exposures to the security vulnerabilities in ATL described in Microsoft Security Bulletin MS09-035
• In downloads with "UseWinInet" property set to false, the temp file for the last downloaded file was not getting deleted after the download is complete
• In requests with chunked transfer-encoding turned on or "UseWinInet" property set to false, adding a cookie created a separate Cookie header
• "Response" property returned duplicated server response after uploads over 2 GB, or with "TransferEncoding" property set to 1 or "UseWinInet" property set to false
• FileManager's "FileExists" method did not recognize files with certain unicode characters in their name
• FileManager's "GetFile" method threw error "The filename, directory name, or volume label syntax is incorrect" for files with unicode characters in their name

• Downloads over SSL failed when UseWinInet disabled
• Visual Progress Indicator showed incorrect Estimated Time and Bytes Transferred
• Extra temp file created in USERPROFILE location on client machine during downloads

• XFile version 2.4.0 did not send the custom X-Content-Length header required by FileUpEE for chunked uploads
• Browser crashed when accessing certain parts of the XFResume object
• Downloads over 4 GB with the visual control terminated before completion

• Security fixes for buffer overflow vulnerabilities
• Error: "Could not create RequestRecord" with resumable uploads and downloads
• IE crashed when calling AddFormElement
• Visual control and client-side progress indicator displayed incorrect size for files over 2 GB
• Browser crashes during downloads
• "Error: Source=null Description=null" masked true error
• Large chunked 3-tier uploads failed
• FileManager: Attributes property of File object was not working correctly
• Filemanager: DeleteFolder method could not delete sub-folder

• Resumable uploads can now be done asynchronously. Previously, the Start method had an asynchronous option, but the Resume method did not*
• TopFolder property now creates directory structure for storing resume info if the directories do not exist*
• XFResume.IsOpen method was added to determine if the object is already open to a location*

• Errors downloading files with long URL using the visual download control
• Because of 2 GB limit in ASP.NET's maxRequestLength setting, XFile's threshold was lowered from 4 GB to 2 GB for automatically switching uploads to chunked transfer encoding and the custom HTTP client. (equivalent of setting oXFRequest.TransferEncoding = 1 and oXFRequest.UseWininet = false)
• Certain cases were causing an "Operation timed out" even though no timeout occurred
• TransferStatusChanged event did not return TransferCancelled status when user aborted the transfer
• TransferStatusChanged event did not return TransferTimedOut status after client-side timeout
• When SaveLocationPromptType set to 2, hitting cancel in the save dialog caused browser crash
• When SaveLocationPromptType set to 1, hitting cancel in the folder dialog caused browser hang
• If user cancelled uploads and TransferStatusChanged events were being handled, browser would sometimes crash
• Chunked-encoded uploads caused erroneous timeout error
• Files uploaded or downloaded with the visual objects did not appear "checked" if the upload completed through a resume operation
• Calling RemoveAll on the visual upload and download controls did not remove files from the underlying file collection of the XFRequest object
• Setting client-side timeout value to 0 caused browser freezing
• Error thrown when xfclient.dll not registered referred to incorrect dll name
• Buffer overrun in SSL transfers caused browser crash
• Issue with XFResume.Close prevented the XFResume object from being reopened*
• XFile returned non-JobId folders when checking ResumeInfo collection*

• Added new methods to sync events when XFile is run in scripting or VBA environments
• New Event for the XFRequest object: OnStatusChange

• Changed the way cached headers were being added to the Resumed Request
• When not using WinInet, sometimes Response headers were being lost
• In some cases, chunked-transfer encoded downloads were not being correctly interpreted as failures

• Renamed WebClnt.Dll to XFClient.dll due to a naming conflict with a Windows XP dll
• Under certain circumstances, the Request Record for resumable downloads would not be updated, resulting in the same file being concatenated with itself
• In some cases, a DNS or Unresolvable Host error would return a Response Status of 0 and would not throw an exception

• Under some circumstances, authentication did not work

• On Windows 95/98/ME, using the Visual Upload Control (AXFFile) caused IE to crash intermittently
• The Add File Selector for the Visual Upload Control (AXFFile) on some foreign versions of Windows did not render correctly
• Some file view types (for the Add Files Selector) did not work on Windows XP
• When forcing a multipart/form-data request that does not contain files, an extra CRLF appeared after the last form element
• An error occurred when setting DiscardResponse to true when using the Visual Download Control (AXFFileDownload)

• The download folder selection dialog was missing the folder list view when used asynchronously

• Customize column headings for the upload and download visual controls.
• New Property: FileNameColumnWidth = 0 - 100. This is the percentage of the width of the list view. Also, setting AXFFileDownload.HideURL to false now sets the width of the URL column to 0 or this property to 100.
• Ability to disable the animated gif image in the progress indicator.
• OpenAfterDownload functionality is now customizable.
• New Property OpenAfterDownloadIndex on the XFrequest object. Possible values and their meaning:
  • 0: Open all files until the first error occurs, default for backwards compatibility
  • -1: Open all files, unless an error occurs for that file
  • i: Open only the specified index (1-based)
• New method OpenInApplication() on the XFFile object. This can be used in conjunction with the DownloadError object to open files after download.
• Ability to use our visual progress indicator with a non-visual file transfer: added the XFRequestStream property to the XFRequest object.
• Added better control of File Selector (part of AXFFile). The following new properties and methods have been added:
  • FileViewType = SAFileViewType. The default is List. SAFileViewType { LargeIcons = 0, SmallIcons = 1 List = 2, Details = 3, Thumbnails = 4 }
  • FileSelectorWidth = 400 - 1200 pixels
  • FileSelectorHeight = 200 - 800 pixels
  • AddFileSelectorFilter(FilterDescription, FilterPattern) Description: The FilterDescription is a display string that describes the filter (for example, "Text Files"), and the FilterPattern specifies the pattern (for example, "*.TXT", "*.*", "a*.*", "*the*.*"). To specify multiple FilterPatterns for a single display string, use a semicolon to separate the patterns (for example, "*.TXT;*.DOC;*.BAK"). A pattern string can be a combination of valid file name characters and the asterisk (*) wildcard character. Do not include spaces in the pattern string.
  • ClearFileSelectorFilters Description: Clears all filters. The dialog will use "All Files (*.*)"
• New Property: IsActive, used when XFile is executed asynchronously to determine if XFile is transferring a file or is capable of starting another transfer.

• When using XFile asynchronously the internal mime composer was being reset prematurely.
• File selection dialog flickered.
• Canceled property always returned True after Start() returned.

• When setting the property UseWinninet=False, multiple download requests will fail after the first one.

• Canceling a transfer when using WinInet was causing a "can't create file" exception and/or crashing IE.
• URLEncoding failed on some special characters.

• Unlimited upload and download size.*
• Resumable uploading and downloading.*
• Support for Windows Integrated, Basic, and Anonymous authentication.
• New properties that specify whether XFile should set a download destination directory or prompt users to select a directory for downloaded files.
• Ability to check if an error occurred downloading one or more files.

• Memory leak with each transfer request.

• Support for the request method Head. You can now set XFRequest.RequestMethod to "Head".
• Dynamic Basic authentication - you can prompt users for user name and password if these are required but are not pre-defined.

• When uploading to a Windows 2000 server, cancelling the upload would freeze the browser.
• In asynchronous transfers, events could not be sinked by the Visual Basic event handler.
• Memory leak when transferring large form values.
• In URL encoded POSTs (where enctype is "application/x-www-urlencoded") containing Unicode data, the data was not URL encoded. The Unicode data was converted to bytes using the current system's charset.
• In POSTs that contain form data but do not contain files, an error occurred when the form data exceeded 4096 characters.
• The ActiveX download control did not allow renaming of local files.
• FileManager:
  • On Windows 2000, FileManager did not include the permission component Synchronize when applying the permission groups Execute, Modify, List, and Write to files and folders.

• FileManager:
  • The AllowAccess and DenyAccess methods failed on Windows 2000 and Windows XP.

• FileManager:
  • MD5 hashing failed on Windows 95, 98, and ME platforms.
  • The PermItem.RemoveEntry method failed when called to remove an item from the Permissions collection of a File or Folder object.

• FileManager:
  • Unable to access Drive property from File or Folder object with a UNC path.
  • Unable to set Owner for a folder.

• The visual upload control's Enabled property now works as both a parameter (<PARAM >) and a property.
• Occasional crashes when posting more than 16 KB from a form.
• Occasional crashes when using XFile asynchronously in a Visual Basic form.
• FileManager Encryption/Decryption generated errors on Windows 95/98.

• The following properties are added to FileManager component.
  • AccountServer property is added to both File and Folder objects to resolve user account when changing ACLs. It's Read/Write.
  • Checksum property is added to File object to return the checksum value based on MD5 hashing algorithm. It's Read-Only.

• The ActiveX Visual Controls support following parameters with appropriate values.
  • AXFFile - ActiveX Upload Control
    • <PARAM NAME="EnableAddButton" VALUE="-1">
    • <PARAM NAME="EnableRemoveButton" VALUE="-1">
    • <PARAM NAME="EnableUploadButton" VALUE="0">
    • <PARAM NAME="AddButtonText" VALUE="Add Files">
    • <PARAM NAME="RemoveButtonText" VALUE="Remove Files">
    • <PARAM NAME="UploadButtonText" VALUE="Upload Files">
  • AXFFileDownload - ActiveX download Control
    • <PARAM Name="HideURL" VALUE="0">
    • <PARAM Name="EnablePopUpMenu" VALUE="-1">
  • AXFFileProgress - ActiveX transfer progress windows Control
    • <PARAM NAME="EnableCancelButton" VALUE="-1">
    • <PARAM NAME="CancelButtonText" VALUE="Cancel">
    • <PARAM NAME="HideURL" VALUE="0">

• When getting the Canceled property, there is pointer error returned..
• When server side response page doesn't return anything, there is a "Insufficient memory" error message.

• The ActiveX upload control's Reset method now enables the control's Add button.
• New XFRequest.Response optional parameter allows you to return one of three data types: string, array of variants, or array of bytes.

• Inability to access File object by passing index to AXFFile object's Files collection.
• FileManager
  • TextStream memory leak when using the TextStream object to read lines longer than 128 characters.
  • DenyAccess method did not work correctly with the File object.
  • SearchWildCard property did not work with the Folder object.

• New RSA encryption types added: SARSAHIGH (3) and SARSALOW (4).

• Two Fish encryption/decryption failure on files larger than 1K.
• Failure of RevertToSelf method in Visual Basic.
• Trustee names on a remote NT member-server could not be displayed.
• Access Control List (ACL) corruption after FileManager applied changes to ACLs on Windows NT system.

• The SAXFile ActiveX control no longer locks uploaded files.
• Issues affecting FileManager enumerating root directories or files with Win95/98/Me platform have been resolved.
• Files created with Archive no longer have issues hanging with certain directories.