Category: Dotfuscator Pro Change Log

Enhancements

• Improved renaming of properties referenced in XAML files
• Added a comprehensive error message when using invalid renaming schemes for Xamarin.Android projects
• Added smart obfuscation rules for compiled XAML

Important Compatibility Changes

• Dotfuscator distributed as a Nuget package targets .NET 6 instead of previously .NET Core 2.1.
• Dependencies updated to the newer version of the libraries used by Dotfuscator.

Enhancements

• Tamper Check support is added for .NET Core 3.1/.NET 5+.
• Debugging Check support is added for .NET Core 3.1/.NET 5+.
• Additional license status messages are displayed in the CLI and MSBuild output.
• Changing the Product License does not require the client to be restarted anymore.
• The new signing methods are used instead of the deprecated ones for Android Pie (API Level 28) and newer OSes with Tamper Check.
• Added a Readme file for the Dotfuscator NuGet package for a more seamless setup experience.
• Added a new “force_nuget_tools” global option.
• [This release may include protection enhancements not described here]

Functional Changes

• Merged the Evaluation (Free Trial) and Professional version clients so that the PreEmptive Licensing Server tells the client how to behave. The client does not have to be reinstalled upon upgrading from Evaluation to Professional anymore.
• Forward slashes are being used by default in the config file for better cross-OS support.
• Version “6.0.0” of Microsoft.NETCore.ILAsm and Microsoft.NETCore.ILDasm NuGet packages are used by default (instead of “5.0.0” in the previous version of Dotfuscator), unless you override this value in the “DOT_ILTOOLS_CORE_VERSION” property.

Fixes

• Display that Linking is not supported for .NET Core/.NET 5+ projects instead of displaying an unrelated error message.
• Fixed an issue when Root Check for Xamarin.Android returns false-positive results on certain Android devices.

Enhancements

• Metadata of NET Core/.NET 5+ assemblies will be kept after protection.
• Added SmartObfuscation support for Enum.TryParse.
• Removed license keys from report files.
• Added support for the .NET 5 “Unmanaged” IL calling convention.
• This release may include protection enhancements not described here.

Fixes

• Fixed unclear error message if the stack trace file is missing from the Lucidator input.
• Fixed incorrect indication of “unmatched rules” for Renaming exclusions.
• Fixed the config file generation for directory inputs.
• Fixed an issue with the Unprintable Renaming scheme for Nullable types.

Enhancements

• Added full support for default interface methods.
• Added option to disable the renaming of managed resources.
• User Guide improvements, including a new Release Checklist page to explain how to release an app which is protected by Dotfuscator.
• This release may include protection enhancements not described here.

Functional Changes

• When using Automatic Input Management, such as with the recommended Protect Your App instructions, the Config Editor’s View menu will no longer allow access to report files if there could be multiple reports that vary by build configuration and platform. To access the full set of reports, check the DotfuscatorReports directory.
• In cases where Dotfuscator downloads ILDasm and ILAsm tools via NuGet, you can now specify the NuGet feed, username, and password via environment variables. This should only be necessary if you do not have access to the public nuget.org feed.
• When using an internet proxy requiring authentication, you can now specify the username and password via environment variables for Dotfuscator to use for licensing communications. For details, see Internet Connection Requirement.

Fixes

• Fixed issues related to renaming obfuscation.
• Fixed an issue where strong name re-signing doesn’t support spaces in the path to the key file.
• Fixed an issue where Automatic Input Management would fail if a solution contains a non-filesystem path to a project. For instance, when an “Existing Website” is added to a solution, the solution can contain a web address. In these scenarios, Dotfuscator now warns and continues.
• Fixed an issue where Dotfuscator errors when protecting an assembly whose name contains netstandard.
• Fixed an issue where Dotfuscator errors when processing an assembly which has type forwards to nested types.
• Fixed an issue where the Output tab in the Config Editor would not indicate types which were removed by Dotfuscator.
• Fixed other minor issues.

Enhancements

• Dotfuscator’s MSBuild integration now works with the .NET 5 SDK.
• Additional improvements to the .NET 5 support.
• Documentation improvements.
• Condensed renaming results on the Output tab.
• Improvements to Licensing related UI.
• This release may include protection enhancements not described here.

Functional Changes

• When the PREEMPTIVE_TELEMETRY_OPT_OUT environment variable has an unrecognized value, Dotfuscator will now warn and treat the variable as unset instead of giving an error.

Fixes

• Fixed runtime issue that could occur after renaming types that implement (or extend) types via generic instantiations nested more than two levels.
• Fixed selecting the wrong version of ILasm and ILdasm to use in some cases.

Reading Time: < 1 minute

Change Log – Version 6.1.0 – Release Date November 19, 2020

Enhancements

• Support for signing assemblies when running under .NET Core and .NET 5 on non-Windows.
• Support for Nullable Attributes.
• Config Editor improvements.
• This release may include protection enhancements not described here.

Reading Time: < 1 minute

Change Log – Version 6.0.1 – Release Date April 30, 2020

This is a new major version of Dotfuscator Professional.
See Upgrading from Dotfuscator 4 for details on how to migrate from the previous version of Dotfuscator Professional to this version.

Note that this changelog only covers the changes since the 6.0.0-beta release.
See the 6.0.0-beta changelog for the list of changes between 4.x and 6.0.0-beta.
There are substantial changes described there, including:

• Support for running Dotfuscator’s build components on macOS and Linux, .NET Core, and Mono.
• A new structure for Dotfuscator’s NuGet package.
• Removed features, including the Visual Studio integrated UI, which was replaced with an MSBuild integration that supports Visual Studio, Visual Studio for Mac, Visual Studio Code, and command line build tools.

Reading Time: 3 minutes

Change Log – Version 6.0.0-beta – Release Date December 19, 2019

This is a beta release of Dotfuscator.
Please see the Beta Release Notes for important information.

This is a new major version of Dotfuscator Professional.
See Upgrading from Dotfuscator 4 for details on how to migrate from the previous version of Dotfuscator Professional to this version.

Reading Time: < 1 minute

Change Log – Version 4.43.3 – Release Date December 12, 2019

Fixes

• Fixed performance issue with saving in the Dotfuscator Config Editor.
• Worked around issue where the .NET 4.8 SDK ILDasm introduces unparseable IL for the Double.NaN field.
• Fixed issue in the MSBuild targets integration preventing the SolutionDir property from being used as part of the HintPath of a reference.
• The Dotfuscator Config Editor no longer crashes when debugauto is set and an input assembly in a subdirectory references another input in a different directory.