GleamTech.FileUltimate 9.0.5

.NET Standard 2.0 This package targets .NET Standard 2.0. The package is compatible with this framework or higher. .NET Framework 4.7.2 This package targets .NET Framework 4.7.2. The package is compatible with this framework or higher.
There is a newer version of this package available.
See the version list below for details. 
dotnet add package GleamTech.FileUltimate --version 9.0.5                

                    
                

            
NuGet\Install-Package GleamTech.FileUltimate -Version 9.0.5
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package. 
<PackageReference Include="GleamTech.FileUltimate" Version="9.0.5" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
paket add GleamTech.FileUltimate --version 9.0.5                

                    
                

            
#r "nuget: GleamTech.FileUltimate, 9.0.5"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package. 
// Install GleamTech.FileUltimate as a Cake Addin
#addin nuget:?package=GleamTech.FileUltimate&version=9.0.5

// Install GleamTech.FileUltimate as a Cake Tool
#tool nuget:?package=GleamTech.FileUltimate&version=9.0.5

FileUltimate is an ASP.NET File Manager and Uploader
which supports ASP.NET Core 5.0+, ASP.NET Core 2.1+, ASP.NET MVC 3.0+ and ASP.NET WebForms 4.7.2+ web applications/web sites.

Integrate a file manager into your ASP.NET application or site rapidly.
- Browse and manage files with access control.

- Accept files with the advanced upload functionality.

- Offer a structured and neat download area.

- Preview documents (70+ file formats, including PDF © Microsoft Office), images, audios and videos.

Note: This package contains a fully working version of the product, however without a license key it will run in trial mode.

Product Compatible and additional computed target framework versions.
.NET net5.0 was computed.  net5.0-windows was computed.  net6.0 was computed.  net6.0-android was computed.  net6.0-ios was computed.  net6.0-maccatalyst was computed.  net6.0-macos was computed.  net6.0-tvos was computed.  net6.0-windows was computed.  net7.0 was computed.  net7.0-android was computed.  net7.0-ios was computed.  net7.0-maccatalyst was computed.  net7.0-macos was computed.  net7.0-tvos was computed.  net7.0-windows was computed.  net8.0 was computed.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed. 
.NET Core netcoreapp2.0 was computed.  netcoreapp2.1 was computed.  netcoreapp2.2 was computed.  netcoreapp3.0 was computed.  netcoreapp3.1 was computed. 
.NET Standard netstandard2.0 is compatible.  netstandard2.1 was computed. 
.NET Framework net461 was computed.  net462 was computed.  net463 was computed.  net47 was computed.  net471 was computed.  net472 is compatible.  net48 was computed.  net481 was computed. 
MonoAndroid monoandroid was computed. 
MonoMac monomac was computed. 
MonoTouch monotouch was computed. 
Tizen tizen40 was computed.  tizen60 was computed. 
Xamarin.iOS xamarinios was computed. 
Xamarin.Mac xamarinmac was computed. 
Xamarin.TVOS xamarintvos was computed. 
Xamarin.WatchOS xamarinwatchos was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
9.2.0 235 12/1/2024
9.1.3 590 10/9/2024
9.1.2 129 10/4/2024
9.1.1 267 9/9/2024
9.1.0 174 9/1/2024
9.0.7 272 8/17/2024
9.0.6 233 8/8/2024
9.0.5 113 8/6/2024
9.0.3 97 8/1/2024
9.0.2 104 7/29/2024
9.0.0 170 7/22/2024
8.8.8 500 5/3/2024
8.8.7 280 4/18/2024
8.8.6 2,231 8/27/2023
8.8.5 3,528 4/23/2023
8.8.0 1,847 4/16/2023
8.7.6 1,551 4/11/2023
8.7.5 1,551 4/7/2023
8.7.0 1,636 4/3/2023
8.6.1 1,701 3/7/2023
8.6.0 1,715 2/23/2023
8.5.1 2,481 1/10/2023
8.5.0 3,215 8/14/2022
8.4.8 2,077 6/24/2022
8.4.7 2,770 6/3/2022
8.4.6 1,891 5/25/2022
8.4.5 1,886 5/11/2022
8.4.2 1,873 4/27/2022
8.4.0 1,911 4/20/2022
8.2.1 3,517 3/14/2022
8.2.0 26,949 3/5/2022
8.1.0 2,164 2/22/2022
8.0.0 3,206 11/28/2021
7.9.7 11,912 5/26/2021
7.9.6 3,680 4/28/2021
7.9.5 5,494 4/19/2021
7.9.1 4,836 3/23/2021
7.9.0 7,018 2/16/2021
7.8.5 2,340 1/1/2021
7.8.1 7,742 11/23/2020
7.8.0 1,856 11/17/2020
7.7.7 4,040 11/9/2020
7.7.5 1,745 11/3/2020
7.7.0 3,974 9/15/2020
7.6.0 4,089 8/31/2020
7.5.8 3,030 8/17/2020
7.5.5 2,989 8/6/2020
7.5.2 1,958 7/9/2020
7.5.1 1,847 6/29/2020
7.5.0 1,810 6/23/2020
7.4.5 1,859 6/15/2020
7.4.2 1,887 6/3/2020
7.4.0 1,891 5/22/2020
7.3.7 6,155 1/24/2020
7.3.5 1,893 1/9/2020
7.3.2 4,170 12/6/2019
7.3.1 1,903 11/27/2019
7.3.0 2,468 11/20/2019

## Version 9.0.5 - August 6, 2024

 - **Fixed:** FileManager and FileUploader will render a placeholder tag along with the script tag.
   We need a tag other than script tag for the component even if we render DOM on the client side.
   For example, Kendo UI Window, removes/moves script tags from content html so component is rendered to wrong place
   and not inside the window.

   Kendo UI Window has this code which caused the issue:
     // remove script blocks to prevent double-execution
     element.find("script").filter(executableScript).remove();

 - **Improved:** FileManager and FileUploader will now be resized automatically when the parent DOM element resizes via using
   ResizeObserver in supported browsers. This espacially useful when component width or height is given in percentage and not in pixels.
   For example, when you put FileManager or FileUploader inside Kendo UI Window, they will be resized when the window is maximized.

 - **Fixed:** Attempt to fix intermittent UnauthorizedAccessException in DocumentCache for .lock files.
   This issue is hard to replicate, but in our tests we didn't the observe it again after some locking fixes.
   Let us know if you still get this error intermittently:
     Access to the path "[DocumentCache]:\lock-1hshdfq~w44gb5~w44gb5~lpnqmy.json.lock" is denied due to insufficient permissions.
     Please make sure the current windows identity "computer\user" has the required permissions on the path.