Adding references to FileUltimate assemblies

We also publish to our own NuGet feed as a backup in addition to official nuget.org site and if you want to install from there, run this command:

Install-Package GleamTech.FileUltimate -Source https://get.gleamtech.com/nuget/default/

If you prefer using the user interface when working with NuGet, you can also install the package this way:

1. Add GleamTech's own NuGet feed first to be able to find GleamTech's packages. Go to Tools -> NuGet Package Manager -> Package Manager Settings and then click the + button to add a new package source. Enter GleamTech in Name field and https://get.gleamtech.com/nuget/default/ in Source field and click OK.

2. Go to Tools -> NuGet Package Manager -> Manage NuGet Packages for Solution, select GleamTech or All in the Package source dropdown on the top right. Now enter GleamTech.FileUltimate in the search field, and click Install button on the found package.

For a legacy "ASP.NET Core 2.1 on .NET Framework" project, make sure you have the following additional packages with these last supported versions in your project (update them in Nuget Package Manager if necessary):

• Microsoft.AspNetCore 2.1.7
• Microsoft.AspNetCore.Mvc 2.1.7
• Microsoft.AspNetCore.Session 2.1.7

For an "ASP.NET Core on .NET Core 3.0+/.NET 5.0+" project, these dependencies will be pulled by NuGet Package Manager automatically so you don't need to do any additional steps.

The other DLLs in the same folder, i.e. GleamTech.ImageUltimate.dll, GleamTech.VideoUltimate.dll and GleamTech.DocumentUltimate.dll are assemblies that FileUltimate depends on for some of the features. They are separate assemblies as they are also standalone products with the same names. MSbuild or Visual Studio will automatically copy these 3 DLLs along with the main referenced assembly GleamTech.FileUltimate.dll to your bin folder during build so they don't need to be referenced directly (unless you are using these products separately in the same project and you have a license for them). Note that even without these 3 DLLs, FileUltimate will work but it will just turn off the corresponding features such as generating image or video thumbnails or the document viewer. So with this modular approach, you can opt-out of the features you do not need by excluding the corresponding DLL, i.e. MSBuild or Visual Studio would automatically copy a dependency only if that DLL is found in the same folder as the main referenced DLL so you can simply delete a DLL in the extracted folder to opt-out.