Dotfuscator CE 5.32.0 – Release Date September 2017

Categories
Dotfuscator CE Change Log

Published on September 21, 2017 by PreEmptive Admin

Reading Time: 2 minutes

Change Log – – Version 5.32.0 – Release Date September 2017

Enhancements

  • A new user-friendly interface for configuring Checks has been added.
    • Tamper Checks, Debugging Checks, and Shelf Life Checks are now configured using the new Checks sub-tab. They can no longer be configured as extended attributes in the Instrumentation sub-tab.
    • A Check, when configured in the user interface, can now target multiple methods. Checks that are configured by in-code attributes only target the method they annotate.

  • Obfuscation of apps made with the Unity game engine is now supported. Please see the User Guide for details.
    • Supported app platforms: PC, Mac, and Linux Standalone, Android, iOS, and Windows Store (UWP).
    • Supported scripting backends: .NET and Mono.
  • Obfuscation of .NET Core 2.0 and .NET Standard 2.0 assemblies is now supported.
  • Improved support for Xamarin code and XAML so fewer renaming exclusions are required.
  • Custom assembly load paths can now be configured. This allows Dotfuscator CE to find assemblies located in non-standard locations.
  • Registered users now have the ability to automatically decode obfuscated stack traces.
  • The User Guide has been updated to be easier to read and use.
  • The command line interface can now be used in a specialized Dotfuscator Command Prompt, preventing the need to find the executable and add it to your path in a standard Windows command prompt.
    • You can access the prompt from within the standalone user interface by going to the Tools menu and selecting Dotfuscator Command Prompt. If you have a Dotfuscator config file loaded when you do this, the prompt will start in the directory of that config file.
  • The command line interface will now only display usage help if requested (via the /? or /?? arguments, or a lack of arguments) or if the arguments provided are invalid. Other errors no longer display usage help.
  • The user interface now abbreviates the paths of input assemblies in tree views. The full paths are now provided by tool tips.
  • Dotfuscator now switches to the Results page after a build. This behavior can be disabled via a checkbox on the Results page.
  • Sample projects included with Dotfuscator have been updated.

Functional Changes

  • In order to continually improve quality, collecting basic system configuration is no longer optional. Users can still opt out of sharing additional information such as feature usage and configuration information.
    • No personally identifiable information is ever collected.
  • Newer Microsoft-authored assemblies will now be automatically treated as artifacts when present in a package, as certain older assemblies were.
  • The command line interface will now show a renaming summary at the end of the build.
  • InsertTamperCheckAttribute and InsertShelfLifeAttribute have been renamed to TamperCheckAttribute and ShelfLifeCheckAttribute. The old names remain for backwards compatibility.

Fixes

  • Corrected an issue where Dotfuscator added a reference to mscorlib to assemblies that did not reference it before processing
  • Corrected issues with Dotfuscator and Lucidator decoding obfuscated stack traces.
  • Corrected an issue where Dotfuscator fails to resolve assembly references if a directory is inaccessible.
  • Corrected an issue where Dotfuscator does not detect tools included with certain Windows Kits in the Windows 10 Creators Update.
  • Fixed other minor issues.