ImageUltimate v3.3.5

Version 3.3.5 - October 31, 2018

• Improved: Stability of image processing.

Included example projects:

• ASP.NET WebForms (C#)
• ASP.NET WebForms (VB)
• ASP.NET MVC (C#)
• ASP.NET MVC (VB)
• ASP.NET Core (C#)

ImageUltimate v3.3.0

Version 3.3.0 - October 12, 2018

• Added: Fixing orientation for read images automatically. The photos taken in a digital camera usually
  have an EXIF 'Orientation' tag that is set using a gravity sensor and these photos need to be adjusted
  so that its orientation is suitable for viewing (i.e. top-left orientation). New properties and methods
  for this feature:

  • ImageUltimateConfiguration.AutoFixOrientationEnabled -> The default is true so from now on all read images
    are fixed automatically.

  • ImageTaskBase.FixOrientation -> You can manually call this method for a specific image if you want to keep
    the above global setting as false).

  Note that for seeing new orientation fixing in effect you will need to delete corresponding cache file for an image
  if it was already cached by previous versions.

• Improved: Stability of image processing.

Included example projects:

• ASP.NET WebForms (C#)
• ASP.NET WebForms (VB)
• ASP.NET MVC (C#)
• ASP.NET MVC (VB)
• ASP.NET Core (C#)

ImageUltimate v3.2.5

Version 3.2.5 - September 5, 2018

• Improved: Stability of image processing.

Included example projects:

• ASP.NET WebForms (C#)
• ASP.NET WebForms (VB)
• ASP.NET MVC (C#)
• ASP.NET MVC (VB)
• ASP.NET Core (C#)

ImageUltimate v3.2.0

Version 3.2.0 - August 1, 2018

• Fixed: Since v3.1.0, library failed to work on .NET versions before 4.6 due to MissingMethodException (related to
  compiler emitting Array.Empty method call which only exists in .NET 4.6).
  Now it works on .NET 4.0 and above as expected.

• Improved: Stability of image processing.

Included example projects:

• ASP.NET WebForms (C#)
• ASP.NET WebForms (VB)
• ASP.NET MVC (C#)
• ASP.NET MVC (VB)
• ASP.NET Core (C#)

ImageUltimate v3.1.6

Version 3.1.6 - July 16, 2018

• Fixed: "Input string was not in correct format" error when setting LicenseKey property when you have an invalid
  version string in AssemblyFileVersion attribute of your assembly. For example using asterisk (e.g. "1.0.184.*")
  is not valid for AssemblyFileVersion, it's only valid for AssemblyVersion (compiler only converts asterisk to
  number only for this attribute). Now even if you have invalid version (non-numeric) in AssemblyFileVersion
  attribute, the parsing error will be ignored.

• Improved: Stability of image processing.

Included example projects:

• ASP.NET WebForms (C#)
• ASP.NET WebForms (VB)
• ASP.NET MVC (C#)
• ASP.NET MVC (VB)
• ASP.NET Core (C#)

ImageUltimate v3.1.5

Version 3.1.5 - June 25, 2018

• Improved: Stability of image processing.

• Improved: Documentation.

Included example projects:

• ASP.NET WebForms (C#)
• ASP.NET WebForms (VB)
• ASP.NET MVC (C#)
• ASP.NET MVC (VB)
• ASP.NET Core (C#)

ImageUltimate v3.1.1

Example projects for WebForms (C#), WebForms (VB), MVC (C#) and MVC (VB) are included.

Version 3.1.1 - June 14, 2018

• Improved: Updated GleamTech.Core.

ImageUltimate v3.1.0

Example projects for WebForms (C#), WebForms (VB), MVC (C#) and MVC (VB) are included.

Version 3.1.0 - May 22, 2018

• Added: "ASP.NET Core on .NET Framework" support. ASP.NET Core uses a completely new web engine different than
  System.Web but now you can use GleamTech products on both classic ASP.NET and ASP.NET Core with the same net40 DLL
  as we abstracted classes like HttpContext, HttpRequest and HttpResponse etc. and we implemented a Middleware for
  mimicking HttpModule and HttpHandler. So our DLL auto-magically works regardless of whether you are running
  under classic ASP.NET or ASP.NET Core. Note that "ASP.NET Core on .NET Core" is a different platform and it's not
  supported yet because it requires porting all the code from .NET Framework runtime to .NET Core runtime so it
  requires a new DLL and .NET Core runtime does not provide all of the APIs yet. Minimum supported version is
  ASP.NET Core MVC 2.0.3 on .NET Framework 4.6.1 (this is because 2.0.3 fixes a bug related to referencing
  external DLLs in a razor page).

• Added: New example project for "ASP.NET Core on .NET Framework", please refer to it for info on sample usage.
  Also updated docs with Getting Started article for the new platform.

• Changed: License keys are changed so please go to https://www.gleamtech.com/upgrade and acquire a new license
  key if you want to use this version (or higher). If your one year maintenance has not ended, you will receive a
  new free license key on the same page.

• Improved: Stability of image processing.

ImageUltimate v3.0.6

Example projects for WebForms (C#), WebForms (VB), MVC (C#) and MVC (VB) are included.

Version 3.0.6 - April 20, 2018

• Improved: Stability of image processing.

ImageUltimate v3.0.5

Example projects for WebForms (C#), WebForms (VB), MVC (C#) and MVC (VB) are included.

Version 3.0.5 - April 11, 2018

• Fixed: Handler routing was not working (HTTP 404) in ASP.NET Development Server included in Visual Studio 2010
  due to how it handled Request.PathInfo differently from IIS/IIS Express.

• Improved: Removed ImageModule and made use of the new handler routing (no need for an additional HttpModule
  as WebActivationModule is now the central and only module for GleamTech products)