Change Log - Version 4.37.0 - Release Date August 21, 2018
This release includes a brand-new way to use Dotfuscator, designed to make it easier to get started, easier to integrate into your build, and easier to maintain your configuration. This new approach is built on top of our existing feature set, so current users do not have to adopt it, but we are suggesting it as the primary way that all users use Dotfuscator, from now on.
To get started, you insert a few lines into your existing Visual Studio project file (i.e. a
.csproj file or other MSBuild file).
Then you run a
Release build as usual, and Dotfuscator automatically generates a config file for you (with default settings) and automatically protects your app.
From there, our new Automatic Input Management feature will automatically update your Dotfuscator config as you add or remove projects from your Visual Studio solution.
This new approach works for nearly all our supported platforms, including .NET Framework, .NET Core, Xamarin, and UWP. It supports incremental builds on most platforms, and will integrate well with any downstream build steps like packaging and signing. (Note that it does not yet support linking.)
In future releases, we plan to provide a new Visual Studio integrated UI that makes the initial setup even easier. We have therefore deprecated our current Visual Studio integration, and it will be removed when we publish the new integration in a future release.
Note that we have also updated our terminology: a "Dotfuscator project" is now consistently referred to as a "Dotfuscator config" to avoid ambiguity with MSBuild project files, and Dotfuscator's "Standalone GUI" is now Dotfuscator's "Config Editor".
- Running Dotfuscator now minimally requires .NET Framework v4.6.1 to be installed on the machine. (Previously it required v4.5.2.) Dotfuscator can still process applications from earlier frameworks, back to .NET 1.x.
- Telemetry/PreEmptive Analytics has been deprecated. It will be removed in a future release of Dotfuscator.
- An unconfigured Customer Experience Improvement Program setting is now interpreted as "enabled". To change your participation in this program, launch the Dotfuscator Config Editor, open the Help menu, and select Customer Feedback Options.
- The Visual Studio Integration UI has been deprecated. It will be removed in a future release of Dotfuscator and replaced with a new UI based on the new integration approach described above.
- The contents of the Dotfuscator Professional Quick Start Guide have been merged into the Dotfuscator Professional User Guide.
/makeconfigoption has been deprecated. The new
/genconfigoption should be used instead. Whereas
/makeconfigboth created a new Dotfuscator config and ran Dotfuscator with that config,
/genconfigsimply creates the new Dotfuscator config. Furthermore,
<propertylist>element in the config file, populated with the property values passed in the command line via the
- The Dotfuscator application that edits the Dotfuscator config file (
dotfuscatorUI.exe) is now called "Dotfuscator Pro Config Editor" in the Windows Start Menu, and just "Config Editor" in the UI and documentation.
- Dotfuscator no longer resorts to displaying a Proxy information request dialog when failing to reach PreEmptive's licensing and registration services. The ability to configure Proxy information for this purpose is still available in the Dotfuscator Config Editor.
- To perform an offline activation of Dotfuscator, you will now need to call Support. The Dotfuscator command line option
/offlineactivationhas been removed, and the Dotfuscator Config Editor and the Visual Studio Integration no longer provide an offline activation dialog.
- Inputs specified by the
InputAssembliesproperty on the Dotfuscate MSBuild task are now treated as input assemblies even if they are not also listed in the config file. In other words, inputs specified by the
InputAssembliesproperty are merged with the inputs listed in the config file.
- Dotfuscator no longer fails when an input with an assembly-level inclusion/exclusion rule is removed from the input list in the config. Instead, Dotfuscator will warn that there are orphaned rules.
- Dotfuscator Professional can now be installed, activated, and run under Windows' FIPS mode provided that Dotfuscator is not an Evaluation copy and is used with a perpetual (non-subscription) license.
- The installer will now prompt for a license key and perform the initial activation (if needed), once the primary installation is complete.
- The User Guide has been further reorganized to make it easier to find content. In particular, the "User Interfaces" section was expanded to list all of the tools and integrations that Dotfuscator provides.
- This release may include protection enhancements not described here.
- Fixed an issue where "Visual Studio Build Tools 2017" was listed as an option for installing the Visual Studio integration, which would cause an installation failure if selected.
- Fixed an issue where a file-level inclusion/exclusion rule for a file that does not exist or is not an assembly caused subsequent file-level rules to be ignored.
- Fixed an issue where an unnecessary, renamed
DotfuscatorAttributewas added to an assembly if renaming was enabled and a Root Check was injected.
- Fixed other minor issues.