ImageUltimate v6.6.6

Version 6.6.6 - October 2, 2025

• Improved: AuthenticatedUser.Windows and AuthenticatedUser.Claims used for PhysicalLocation will now also work on
  ASP.NET Core (previously only worked on ASP.NET Classic).
  Also the enum members AuthenticatedUser.Windows and AuthenticatedUser.Claims are made obsolete.
  Use AuthenticatedUser.WebServer and AuthenticatedUser.ClaimsUpn instead.
  These new enum member names are more explanatory for their purpose.

• Improved: Prevent log file name conflicts when multiple Apps sharing App_Data
  For example try file names GleamTech.log, GleamTech-AppName.log, GleamTech-AppName-z0yxh40r.log.
  Also provide environment details (app name, location, os) in GleamTech.log just like AssemblyResolver.log
  when initializing GleamTechConfiguration.

Included example projects:

• ASP.NET Core (C#) - Visual Studio 2019+
• ASP.NET Core on .NET Framework (C#)- Visual Studio 2017+
• ASP.NET MVC (C#) - Visual Studio 2015+
• ASP.NET MVC (VB) - Visual Studio 2015+
• ASP.NET WebForms (C#) - Visual Studio 2015+
• ASP.NET WebForms (VB) - Visual Studio 2015+

ImageUltimate v6.6.5

Version 6.6.5 - September 26, 2025

• Improved: The default value for GleamTechConfiguration.TemporaryFolder will now be [AppData Temporary Folder]
  if current user has read/write access, if not it will be [System Temporary Folder].

  This change is done so that developer is only concerned about write permissions to [AppData Temporary Folder]
  when publishing to production and not system temporary folders such as C:\Windows\Temp.
  This way, everything will be on the table i.e. all generated files (AssemblyResolver files, cache files, log files) will be in a single place.
  Files from old system temporary folder will be migrated/moved to this new location on application startup (if has write access).

  [AppData Temporary Folder] can be different for different environments:

  • For ASP.NET Core apps, the resolved result of ~/App_Data:
    • [AppBase]\wwwroot\App_Data\Temporary
  • For ASP.NET Classic apps, the resolved result of ~/App_Data:
    • [AppBase]\App_Data\Temporary
  • For Console or other non-web apps:
    • [AppBase]\AppData\Temporary

  [System Temporary Folder] can be different for different environments:

  • For ASP.NET Core apps, the result of Path.GetTempPath() which
    depends on "TMP", "TEMP" and "USERPROFILE" environment variables:
    • %WINDIR%\Temp\GleamTech\[AppName]-[AppHash]
    • %LOCALAPPDATA%\Temp\GleamTech\[AppName]-[AppHash]
      (if "Load User Profile" is enabled for AppPool in IIS)
  • For ASP.NET Classic apps:
    • %WINDIR%\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\[AppName]\[AppHash]\GleamTech
    • %WINDIR%\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\[AppName]\[AppHash]\GleamTech
      (if 32-bit AppPool)
    • %LOCALAPPDATA%\Temp\Temporary ASP.NET Files\vs\[AppHash]\GleamTech
      (when debugging in Visual Studio)
  • For Console or other non-web apps, the result of Path.GetTempPath() which
    depends on "TMP", "TEMP" and "USERPROFILE" environment variables:
    • %LOCALAPPDATA%\Temp\GleamTech\[AppName]-[AppHash]
    • %WINDIR%\Temp\GleamTech\[AppName]-[AppHash]
  • For apps running on unix-like platforms:
    • /tmp/GleamTech/[AppName]-[AppHash]

• Improved: ImpersonationContext is improved to support multi-threads and async threads.
  Ensured ImpersonationInfo and LogonCredential do not lose access tokens (re-cache when necessary).

• Improved: TemporaryFolder, FileCache and DbProvider will now do two tries for access, if first one fails,
  will try again by reverting possible impersonation.

• Changed: Removed legacy GleamTechConfiguration.AlphaFileSystemEnabled property.

Included example projects:

• ASP.NET Core (C#) - Visual Studio 2019+
• ASP.NET Core on .NET Framework (C#)- Visual Studio 2017+
• ASP.NET MVC (C#) - Visual Studio 2015+
• ASP.NET MVC (VB) - Visual Studio 2015+
• ASP.NET WebForms (C#) - Visual Studio 2015+
• ASP.NET WebForms (VB) - Visual Studio 2015+

ImageUltimate v6.6.2

Version 6.6.2 - September 10, 2025

• Improved: Stability and performance of image processing and image formats.

Included example projects:

• ASP.NET Core (C#) - Visual Studio 2019+
• ASP.NET Core on .NET Framework (C#)- Visual Studio 2017+
• ASP.NET MVC (C#) - Visual Studio 2015+
• ASP.NET MVC (VB) - Visual Studio 2015+
• ASP.NET WebForms (C#) - Visual Studio 2015+
• ASP.NET WebForms (VB) - Visual Studio 2015+

ImageUltimate v6.6.1

Version 6.6.1 - September 1, 2025

• Improved: Updated GleamTech.Common.

Included example projects:

• ASP.NET Core (C#) - Visual Studio 2019+
• ASP.NET Core on .NET Framework (C#)- Visual Studio 2017+
• ASP.NET MVC (C#) - Visual Studio 2015+
• ASP.NET MVC (VB) - Visual Studio 2015+
• ASP.NET WebForms (C#) - Visual Studio 2015+
• ASP.NET WebForms (VB) - Visual Studio 2015+

ImageUltimate v6.6.0

Version 6.6.0 - August 27, 2025

• Improved: Stability and performance of image processing and image formats.

Included example projects:

• ASP.NET Core (C#) - Visual Studio 2019+
• ASP.NET Core on .NET Framework (C#)- Visual Studio 2017+
• ASP.NET MVC (C#) - Visual Studio 2015+
• ASP.NET MVC (VB) - Visual Studio 2015+
• ASP.NET WebForms (C#) - Visual Studio 2015+
• ASP.NET WebForms (VB) - Visual Studio 2015+

ImageUltimate v6.5.4

Version 6.5.4 - July 3, 2025

• Improved: Updated GleamTech.Common.

Included example projects:

• ASP.NET Core (C#) - Visual Studio 2019+
• ASP.NET Core on .NET Framework (C#)- Visual Studio 2017+
• ASP.NET MVC (C#) - Visual Studio 2015+
• ASP.NET MVC (VB) - Visual Studio 2015+
• ASP.NET WebForms (C#) - Visual Studio 2015+
• ASP.NET WebForms (VB) - Visual Studio 2015+

ImageUltimate v6.5.3

Version 6.5.3 - May 6, 2025

• Improved: Updated GleamTech.Common.

Included example projects:

• ASP.NET Core (C#) - Visual Studio 2019+
• ASP.NET Core on .NET Framework (C#)- Visual Studio 2017+
• ASP.NET MVC (C#) - Visual Studio 2015+
• ASP.NET MVC (VB) - Visual Studio 2015+
• ASP.NET WebForms (C#) - Visual Studio 2015+
• ASP.NET WebForms (VB) - Visual Studio 2015+

ImageUltimate v6.5.2

Version 6.5.2 - April 18, 2025

• Improved: Updated GleamTech.Common.

Included example projects:

• ASP.NET Core (C#) - Visual Studio 2019+
• ASP.NET Core on .NET Framework (C#)- Visual Studio 2017+
• ASP.NET MVC (C#) - Visual Studio 2015+
• ASP.NET MVC (VB) - Visual Studio 2015+
• ASP.NET WebForms (C#) - Visual Studio 2015+
• ASP.NET WebForms (VB) - Visual Studio 2015+

ImageUltimate v6.5.1

Version 6.5.1 - April 11, 2025

• Fixed: Exception when you have app.UseGleamTech() in your project and when the "Referer" http header contained an invalid URL:

  System.UriFormatException: Invalid URI: The format of the URI could not be determined.
      at GleamTech.AspNet.Core.WebActivationMiddlewareExtensions...
  

  This was observed especially when certain pages like /Customer/Home/Forbidden or /Customer/Error/HandleError were accessed.
  This is because as the original url was invalid, it was redirected to the error pages which contained "Referer" http header
  referring to the original url with the problem.

Included example projects:

• ASP.NET Core (C#) - Visual Studio 2019+
• ASP.NET Core on .NET Framework (C#)- Visual Studio 2017+
• ASP.NET MVC (C#) - Visual Studio 2015+
• ASP.NET MVC (VB) - Visual Studio 2015+
• ASP.NET WebForms (C#) - Visual Studio 2015+
• ASP.NET WebForms (VB) - Visual Studio 2015+

ImageUltimate v6.5.0

Version 6.5.0 - April 1, 2025

• Added: Better multi-platform suppport. Image conversions require native dependencies which we already bundled
  in our DLL for win-x64 and win-x86 platforms. In addition to these, we now also bundle dependencies for these platforms:

  • win-arm64
  • linux-x64, linux-arm64
  • osx-x64, osx-arm64

  Only win-* dependencies are bundled in our DLL and our AssemblyResolver will handle those, i.e automatically resolve them.

  linux-* and osx-* dependencies are bundled only in our NuGet package in runtimes//native folders,
  this is because it's nearly impossible to load/resolve native files in custom folders on non-Windows platforms (especially Linux).
  However .NET SDK handles this issue at build time: At build time, SDK will put runtimeTargets entries in .deps.json file
  for each native file (.dll, .so, .dylib) that come/flow from a NuGet PackageReference.
  This way, .NET Runtime can resolve these native files by reading the .deps.json file.

  So in short, reference our NuGet package (not our DLL directly) especially if you are targeting linux-* and osx-*.

• Improved: Stability and performance of image processing and image formats.

Included example projects:

• ASP.NET Core (C#) - Visual Studio 2019+
• ASP.NET Core on .NET Framework (C#)- Visual Studio 2017+
• ASP.NET MVC (C#) - Visual Studio 2015+
• ASP.NET MVC (VB) - Visual Studio 2015+
• ASP.NET WebForms (C#) - Visual Studio 2015+
• ASP.NET WebForms (VB) - Visual Studio 2015+