DocumentUltimate v4.5.6

Version 4.5.6 - January 29, 2019

• Improved: Support for adding GleamTech assemblies to GAC (Global Assembly Cache), for example using with
  SharePoint On Premise will be possible. In previous versions, the integrated AssemblyResolver failed
  with "Could not load file or assembly 'GleamTech.AssemblyResolver, Version=2.0.0.0, Culture=neutral,
  PublicKeyToken=a05198837413a6d8'" error. This is because AppDomain.AssemblyResolve event is not fired by
  .NET Framework (fusion) when the requesting assembly is installed to GAC. Now with a workaround, the integrated
  AssemblyResolver will be successfully loaded and it will resolve other assemblies.

Included example projects:

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

DocumentUltimate v4.5.5

Version 4.5.5 - January 22, 2019

• Improved: Stability and performance for DocumentCache:

  • Optimized cache folder structure so that access is very fast even when it's crowded (e.g. 20.000 files).
    This will also vastly improve access times when Amazon S3 or Azure Blob location is used for the cache
    (no more unnecessary cache folder listing so fewer requests to cloud storage). The existing cache folder
    will be migrated to the new structure automatically when this version first runs.

  • Cache folder can now be shared with multiple processes reliably as it will use distributed locking.
    Even processes on different machines will be handled via creating lock files within the cache folder.
    For example if you use a network share as the cache folder, different instances of the application will
    reliably share the cache (no unexpected "cache file not found" errors and ensuring the ongoing caching
    is completed only once).

  • Automatic cache trimming (clean up of expired items) is now a background task which is run at regular intervals
    specified via AutoTrimInterval property (default is 20 minutes). In the older version, it required a trigger
    of creating a new cache item. So now auto cache trim is more reliable and efficient.

  • Replaced maxDays constructor parameter with MaxAge property which is a TimeSpan so expiration can now be set
    also in hours, minutes or seconds and not only in days.

  • API changes:

    • DocumentCache(Location location, int maxDays ...) -> DocumentCache(Location location)
    • DocumentCache.MaxAge -> New Get/Set property (replaces maxDays constructor parameter)
    • DocumentCache.WaitTimeout -> New Get/Set property
    • DocumentCache.AutoTrimInterval -> New Get/Set property
    • DocumentCache.LocationString -> New Get property
    • DocumentCache.LocationId -> New Get property
    • DocumentUltimateWebConfiguration.CacheMaxDays -> DocumentUltimateWebConfiguration.CacheMaxAge
    • DocumentUltimateWebConfiguration.CacheWaitTimeout -> New Get/Set property
    • DocumentUltimateWebConfiguration.CacheAutoTrimInterval -> New Get/Set property
    • DocumentUltimateWebConfiguration.EncryptionEnabled -> DocumentUltimateWebConfiguration.CacheEncryptionEnabled

Included example projects:

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

DocumentUltimate v4.5.0

Version 4.5.0 - January 11, 2019

• Improved: DocumentViewer rendering accuracy and performance.

• Improved: Stability, accuracy for Spreadsheet, Presentation and Email formats.

Included example projects:

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

DocumentUltimate v4.4.5

Version 4.4.5 - December 12, 2018

• Fixed: "Parameter is not valid" error when converting Cad formats to image files. If the drawing is too large,
  the image will be limited to maximum 1123x1123 dimension to prevent this Bitmap memory related error.

• Fixed: Sent header for email formats (MSG, EML) in DocumentViewer (or when converting to MHT or PDF) will be
  adjusted to the time zone of current machine (similar to Outlook).
  Full email adresses will be shown in From and To headers (not just display names).
  When converting to HTML, the header will be rendered just like when converting to MHT.

• Fixed: When converting from EML to MSG, the original date was not preserved and the conversion time was displayed in Outlook.

• Improved: Stability, accuracy for Spreadsheet, Presentation, Email and ProjectManagement formats.

Included example projects:

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

DocumentUltimate v4.4.0

Version 4.4.0 - October 31, 2018

• Fixed: Sent header for email formats (MSG, EML) in DocumentViewer (or when converting to MHT or PDF) were being
  rendered corrupted (e.g. "<34pan cla34=headerLineTitle>DaPeTi6e:<34pan cla34=headerLineText>{0}")

• Fixed: The change in v4.3.5 regarding opacity setting for text highlight annotations caused non-black highlights
  to hide the text completely, now it's fixed to be effective only for black color for allowing blacked out text but for
  other colors the opacity will be limited so the text is still visible.

• Improved: Stability, accuracy for Spreadsheet and Email formats.

Included example projects:

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

DocumentUltimate v4.3.5

Version 4.3.5 - 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).

  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.

• Added: New DocumentViewer permissions:

  • ViewAnnotations -> Ability to view annotations of the document.

  • FillForms -> Ability to fill values into form fields of the document

  You can now turn off these features by setting DocumentViewer.DeniedPermissions property.

• Fixed:: When TextWatermark.Text property included CR + LF (\r\n) instead of LF (\n) line ending,
  the watermark was not centered correctly. Now text line endings are normalized before applying.

• Fixed: The opacity setting for text highlight annotations was not being represented correctly in the
  DocumentViewer. For example blacked out text using the Adobe text highlighting feature was no longer
  blacked out in the viewer.

• Improved: Stability, accuracy for Spreadsheet, Presentation, Email and ProjectManagement formats.

Included example projects:

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

DocumentUltimate v4.3.0

Version 4.3.0 - October 4, 2018

• Improved: DocumentViewer rendering accuracy and performance.

• Improved: Beautified DocumentViewer user interface. Bookmarks tree has a new look which is faster and more elegant.
  Full text search panel is now more neat. Unified styles of UI elements like dialogs (notable in print dialog)
  and context menus.

• Added: New "Notes Panel" in DocumentViewer (right-side pane) for exploring and searching annotation comments in
  the document.

• Added: DocumentViewer print dialog now contains "Include Comments" option. This will add comment pages after each
  document page that will include the comments (including replies) of annotations on that specific page.

• Added: DocumentViewer.PrintOptions property. These options will be reflected as default values on the print dialog
  of the viewer. For example you can disable HighQuality print option or adjust the level to increase print speed.

• Fixed: Signatures and other annotations in the documents were not being displayed in DocumentViewer.

• Fixed: German language was not working due to a syntax error in the language file (it was translated by a customer).

• Changed: The path for overriding language files is changed to App_GlobalResources\WebViewer\i18n

Included example projects:

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

DocumentUltimate v4.2.0

Version 4.2.0 - September 5, 2018

• Improved: Stability, accuracy for Spreadsheet, Presentation, ProjectManagement and Email formats.

Included example projects:

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

DocumentUltimate v4.1.5

Version 4.1.5 - August 1, 2018

• Improved: Stability, accuracy for Presentation and Email formats.

Included example projects:

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

DocumentUltimate v4.1.0

Version 4.1.0 - July 16, 2018

• Fixed: Downloading files with unicode characters (e.g. german umlauts) in their names failed on ASP.NET Core.
  This was caused because unencoded version of filename was provided in Content-Disposition header for older
  browsers (utf-8 encoded version was already provided for modern browsers). ASP.NET Core does not allow unencoded
  unicode characters in response header value like ASP.NET Classic. So now alternative file name will be
  transliterated to ASCII for keeping old browser support.

• 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, accuracy for Presentation, Spreadsheet, ProjectManagement and Email formats.

Included example projects:

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