GleamTech.FileUltimate 7.9.0

• .NETFramework 4.0

  • GleamTech.Common (>= 4.5.0)
  • GleamTech.DocumentUltimate (>= 5.9.0)
  • GleamTech.ImageUltimate (>= 4.5.0)
  • GleamTech.VideoUltimate (>= 2.5.3)

• .NETStandard 2.0

  • GleamTech.Common (>= 4.5.0)
  • GleamTech.DocumentUltimate (>= 5.9.0)
  • GleamTech.ImageUltimate (>= 4.5.0)
  • GleamTech.VideoUltimate (>= 2.5.3)
  • System.Drawing.Common (>= 4.7.0)

## Version 7.9.0 - February 16, 2021

 - **Added:** FileManager and FileUploader now supports distributed session (e.g multi-instance on Azure or multi-server environment).

 - **Added:** GleamTechWebConfiguration.DistributedStateMode property which specifies whether distributed state should be used for components.
   The default is DistributedStateMode.Auto.
   In DistributedStateMode.Auto mode, serialization of state objects to session is done only if your application is configured to use distributed session:
   - If your application is configured to use in-process (not distributed) session, ComponentStateManager uses MemoryCache for performance reasons.
     This way we can avoid unnecessary serialization of state objects to session which can cause overhead for requests.
   - If your application is configured to use distributed session, ComponentStateManager uses distributed session,
     i.e. serializes state objects to session so that state is available for cloud or multi-server environment.
   - Distributed session meaning: If session state mode is InProc for ASP.NET Classic or MemoryDistributedCache is set for ASP.NET Core,
     then session is in-process (not distributed). In other cases, session is distributed.

 - **Improved:** FileUploader:
   - Optimized IUploadProvider interface. The providers now receive UploadQueue and UploadItem in method parameters.
   - DefaultUploadProvider now writes each chunk as different file then combine them at the end to support distributed session.
   - Since cookieless session feature, legacy Html4 upload method was broken.
   - MaxFileSize, AllowedFileTypes, DeniedFileTypes will also be checked on server for better security.
   - Default ChunkSize is now only dependent on maxAllowedContentLength only so it will be usually 28.6MB and not 4MB.
     For more information see, https://docs.gleamtech.com/fileultimate/html/optional-upload-configuration.htm
   - Added ItemUploading, ItemUploaded and ItemFailed server-side events.

 - API changes:
   - UploadInfo -> UploadQueue
     - New properties TotalUploadedSizeAsString, ElapsedTimeAsString, TransferRateAsString
   - UploadItemInfo -> UploadItem
     - New properties SizeAsString, UploadedSizeAsString
   - FileUploaderReceivingEventArgs -> FileManagerUploadingEventArgs
     - Validations -> Items
     - Properties except Items are moved into Queue property
   - FileUploaderReceivedEventArgs -> FileManagerUploadedEventArgs
     - Properties except Items are moved into Queue property
   - FileManagerUploadingEventArgs
     - Validations -> Items
     - Properties except Items are moved into Queue property
   - FileManagerUploadedEventArgs
     - Properties except Items are moved into Queue property
   - FileManagerDownloadedEventArgs
     - New properties TotalDownloadedSizeAsString, ElapsedTimeAsString, TransferRateAsString

 - **Changed:** Removed FileSystem property from FileManager events. Pre-events will be raised before opening FileSystem
   and Post-events will be raised after FileSystem is disposed. User can create it if required via e.Folder.GetFileSystem().

 - **Improved:** Completed missing documentation for all classes in FileUltimate.

 - **Improved:** FileManager.Id and FileUploader.Id will throw exception if set to an invalid identifier (e.g. guid.ToString()).
   For HTML and CSS compatibility, Id must begin with a letter ([A-Za-z]) and may be followed by any number of letters,
   digits ([0-9]), hyphens (-), underscores (_).

 - **Improved:** FileManager and FileUploader will throw exception if an event handler is not a static method (or not shared in VB).
   Event handlers need to be static for both preventing memory leaks and allowing serialization to distributed session.

 - **Improved:** Better concurrency for OpenFile and CreateFile in AzureBlobFileSystem, AmazonS3FileSystem and ArchiveFileSystem.
   OpenFile should return a stream containing existing file for FileAccessOption.Write.