Download Dotfuscator

[Yaima President]

PreEmptiveProtection - Dotfuscator provides comprehensive .NET application protection that easily fits into your secure software development lifecycle.Use it to harden, protect, and prune desktop, mobile, server, and embedded applications to help secure trade secrets and other intellectual property (IP), reduce piracy and counterfeiting, and protect against tampering and unauthorized debugging.Dotfuscator works on compiled assemblies without the need for more programming or even access to source code.

It's important to protect your intellectual property (IP).Your application's code contains design and implementation details, which can be considered IP.However, applications built on the .NET Framework contain significant metadata and high-level intermediate code, making them easy to reverse engineer, just by using one of many free, automated tools.By disrupting and stopping reverse-engineering, you can prevent unauthorized IP disclosure, and demonstrate that your code contains trade secrets.Dotfuscator can obfuscate your .NET assemblies to hinder reverse-engineering, while maintaining original application behavior.

It's also important to protect the integrity of your application.In addition to reverse-engineering, bad actors may attempt to pirate your application, alter the application's behavior at run time, or manipulate data.Dotfuscator can inject your application with the capability to detect and respond to unauthorized uses, including tampering, third-party debugging, and rooted devices.

Your copy of Microsoft Visual Studio includes a copy of PreEmptive Protection - Dotfuscator Community, free for personal use.(This free version was previously known as Dotfuscator Community Edition or Dotfuscator CE.)

Dotfuscator Community offers a range of software protection and hardening services for developers, architects, and testers.Examples of .NET Obfuscation and other Application Protection features included in Dotfuscator Community are:

Dotfuscator Community offers basic protection out-of-the-box.Even more application protection measures are available to registered users of Dotfuscator Community, and to users of PreEmptive Protection - Dotfuscator Professional, the world's leading .NET Obfuscator.For information about enhancing Dotfuscator, see the Upgrades page.

Depending on your installation history and version of Visual Studio, you may be currently running Dotfuscator Community 5, the prior major version. If so, you should upgrade, because it is important to ensure your code is being given the latest protection measures. Upgrades are available at no charge.

The first integer of the version, before the first dot ., indicates Dotfuscator's major version. If the first integer is 5, then you should perform the upgrade steps on this page, so that you can take advantage of the latest Dotfuscator 6 features and protection updates.

Visual Studio 2019Dotfuscator Community 6 is included in later versions of Visual Studio 2019 (version 16.10.0 and later).Update Visual Studio 2019 to the latest version. Updating Visual Studio automatically upgrades any Dotfuscator Community 5 installation to Dotfuscator Community 6.

Visual Studio 2017This version of Visual Studio only shipped with Dotfuscator Community 5.However, you can install or upgrade to Dotfuscator Community 6 by going to the Dotfuscator Downloads page and selecting the appropriate download link.

Earlier versions of Visual StudioDotfuscator Community 6 is not supported in these versions of Visual Studio.We recommend upgrading to a newer version of Visual Studio, or upgrading from Dotfuscator Community to Dotfuscator Professional.

If you previously used Dotfuscator 5's command-line interface (CLI) to protect your app, you need to update the path to the CLI in any projects and build scripts that reference it. It includes projects that use Dotfuscator Community's Xamarin integration.

The reason a path to Dotfuscator's CLI may now be invalid is because the names of some of the executables installed with Dotfuscator Community have changed in Dotfuscator 6. This change makes these executable names the same across Dotfuscator Community and Dotfuscator Professional.

The CLI path may also be invalid if you upgrade between major versions of Visual Studio or switch Visual Studio editions, as the Dotfuscator CLI is installed under Visual Studio's installation directory.The symptoms and solution listed below also apply to this scenario.

If you previously used Dotfuscator Community's Xamarin integration to protect a Xamarin app, recall that Dotfuscator is integrated into each individual app project (such as MyProject.Android.csproj and MyProject.iOS.csproj) separately and not into shared library projects.Update all of the app projects that are currently using Dotfuscator.

If one of the old paths is not an absolute path, then you should adjust the new path appropriately based on the context.In the example below, the VSInstallDir environment variable was used in the old path, so the corresponding new path should do the same.

If you are using a source control system, such as Git, then ensure the changes from step 6 are reflected in that system.Distribute these changes to the rest of your team as may be appropriate for your system and organization.

Because dotfuscator.exe refers to the graphical user interface (GUI) in Dotfuscator 5 but refers to the command line interface (CLI) in Dotfuscator 6, be careful when updating build scripts shared across multiple machines.

A machine with Dotfuscator 5 installed that runs a script updated for Dotfuscator 6 causes the script to launch the graphical user interface, instead of the intended command line interface. This may cause the build to succeed despite not applying Dotfuscator's protection, meaning your output packages will NOT be protected.

Dotfuscator Engine Initialization error: PreEmptive Analytics, Authenticode signing, and the Introduce Explicit Method Overrides setting are no longer supported. Please open your Dotfuscator config in the Config Editor which automatically upgrades it.

PreEmptive Analytics, Authenticode signing, and the Introduce Explicit Method Overrides setting are no longer supported. The associated settings have been removed. Please save your upgraded Dotfuscator config.

If you are using a source control system, such as Git, then ensure the changes to the Dotfuscator config file are reflected in that system.Distribute these changes to the rest of your team as may be appropriate for your system and organization.

If you integrated Dotfuscator Community 5 into your Xamarin project, one of the steps required you to download custom MSBuild targets and tasks, such as PreEmptive.Dotfuscator.Xamarin.targets. These targets and tasks have been updated in Dotfuscator Community 6, so you need to replace the old versions with the new versions.

Locate the directory where you initially downloaded these files.The example given in the instructions uses a subdirectory named PreEmptive.Dotfuscator.Xamarin, but you may have downloaded the files into a different directory, which may or may not also have files unrelated to Dotfuscator.

If you are using a source control system, such as Git, then ensure the removal of the old files and addition of the new files are reflected in that system.Depending on the kind of system, these changes may appear as files changing contents, rather than being replaced.Distribute these changes to the rest of your team as may be appropriate for your system and organization.

Dotfuscator allows you to configure certain features via .NET attributes in your source code.If your projects were using such attributes, you may need to update them to address changes in Dotfuscator 6.

The library containing the Check Attributes has changed. In Dotfuscator Community 5, it was distributed as a file alongside Dotfuscator itself. Starting in Dotfuscator Community 6, it is instead distributed as a public NuGet package.

Could not resolve this reference. Could not locate the assembly "PreEmptive.Attributes". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.

Each Check Attribute's ExtendedKey parameters have also been removed.These parameters were ignored in Dotfuscator Community 5, but if your source code used them regardless, remove these usages in order for your project to compile.

Instrumentation attributes were used to configure the PreEmptive Analytics feature in Dotfuscator 5. However, PreEmptive Analytics has been removed in Dotfuscator 6; see the Removed Feature subsection PreEmptive Analytics. As a result, the instrumentation attributes have also been removed.

If you try to build a Visual Studio project that used instrumentation attributes, you may get the same kinds of errors and warnings as noted in Check Attributes, though the attribute names differ (for example, FeatureAttribute instead of TamperCheckAttribute).

To fix these problems, remove all usages of instrumentation attributes from your source code.You also need to remove the assembly references to the library that defined the attributes, PreEmptive.Attributes.dll.(If you were also using the Check Attributes that were defined in this library, they have moved; see Check Attributes above.)

Dotfuscator Community 6 introduces breaking changes from Dotfuscator Community 5. If you have been using Dotfuscator Community 5, this section describes how to deal with the changes that might require build modifications or affect Dotfuscator's output.

If you were using Check Telemetry to report when a Check detects an invalid state (such as when tampering is detected), you can replace it with a custom Application Notification that reports the incident to Azure Application Insights or another service of your choice.

Dotfuscator Community no longer supports Universal Windows Platform (UWP) .appx packages as inputs. You can continue to protect Xamarin apps targeting UWP with the Xamarin integration. To protect other kinds of UWP apps, upgrade to Dotfuscator Professional and follow the Protect Your App instructions.

3a8082e126