GleamTech.FileUltimate 7.3.5

• .NETFramework 4.0

  • GleamTech.Common (>= 4.1.0)
  • GleamTech.DocumentUltimate (>= 5.2.0)
  • GleamTech.ImageUltimate (>= 4.1.0)
  • GleamTech.VideoUltimate (>= 2.1.5)

• .NETStandard 2.0

  • GleamTech.Common (>= 4.1.0)
  • GleamTech.DocumentUltimate (>= 5.2.0)
  • GleamTech.ImageUltimate (>= 4.1.0)
  • GleamTech.VideoUltimate (>= 2.1.5)
  • System.Drawing.Common (>= 4.7.0)

## Version 7.3.5 - January 9, 2020

 - **Improved:** Document Viewer:

   - **Added:** Support for viewing STL File Format (3D Printing).

 - **Improved:** Updated Media Player.

 - **Added:** New GleamTechConfiguration.EnsureAssemblies method which ensures GleamTech's assemblies are loaded and initialized.
   You may need to call this method in entry point/startup of your application, if you receive "Could not load file or assembly ..." errors.

   Some DLLs are embedded inside GleamTech's DLLs and they are resolved automatically when they are requested however
   internal AssemblyResolver should be initialized first and internal AssemblyResolver of each GleamTech DLL can be initialized
   only when a type inside that DLL is accessed first. So in some cases, even a GleamTech DLL is loaded, its AssemblyResolver
   may not be initialized yet (because none of its types is accessed yet). You can observe this behaviour if your application
   calls some methods which scans assemblies for reflection purpose (reflection-only type access does not trigger DLL's module initializer),
   for example ASP.NET Core's endpoints.MapControllers method and SimpleInjector�s RegisterMvcControllers method.
   So to prevent errors on those methods, you can call this method before such methods.

   Note that you should not need to call this method usually for web applications, because it is handled automatically
   as we can know when the application is started by hooking up (automatically in ASP.NET Classic and when you call AddGleamTech and
   UseGleamTech methods in ASP.NET Core).

 - **Changed:** In previous versions, invalid values for GleamTech related configuration keys (e.g in Web.config or appsettings.json) was
   silently ignored (exceptions were swallowed). From now on, invalid property values in config files will throw exceptions just like when
   they are set in code. This is especially useful for "FileUltimate:LicenseKey" property, i.e you should instantly know if you put an invalid license
   key (empty string for "FileUltimate:LicenseKey" property will also throw) without silently falling back to trial mode.