Dotfuscator community edition review

App protection initiatives are subject to the same constraints as any development project: scope, time, and ongoing support. Invest in professional-grade protection with PreEmptive Protection Dotfuscator for. Dotfuscator is something I have seen professionally for decades. It seems like you folks have the most history with Visual Studio. On the contrary. Due to this success, we are pursuing the obfuscation of our mobile code using Xamarin. Close Menu Products Dotfuscator for.

Contact Login. Professional-grade Application Protection. Dotfuscator Community incorporates advanced technologies to facilitate this protection and achieve some size reduction due to renaming to trivial identifiers. See Compare Dotfuscator Editions for additional differences.

If you need to go beyond these limitations, contact PreEmptive Solutions for more information about Dotfuscator Professional. Dotfuscator Editions Dotfuscator is available in two editions: the full featured Dotfuscator Professional , and the free Dotfuscator Community included with Visual Studio. The user guide for Dotfuscator Community.

You may also find the Dotfuscator Professional user guide to be helpful, especially the section concerning Build Agents. The user guide for Dotfuscator Community in Visual Studio and A blog article explaining how to enable and use the Dotfuscator Community command line interface in your build process: Using the Dotfuscator Community command line interface.

The Provision step is required in order to activate the Dotfuscator Community command line interface on the build host. Add the Provision step to your build definition, anywhere before Dotfuscator Community runs. When run, the Provision step sets and exposes a build variable called DotfuscatorCEDir , which points to the location of the Dotfuscator Community command line executable on the build host.

Later steps in your build can use this to invoke Dotfuscator Community e. The Protect task runs the Dotfuscator Community command line interface on the build host using the specified configuration file and arguments. Sign in. Reusable code implies there is contingent code that handles many cases — however, in any given application, you typically only use one or two of those many cases. Pruning figures that out and rips out all the unused code from the compiled IL it never touches source.

Pruning's most visible result is the reduction in size of the executable. For many applications that are distributed on CD-ROM, the size of the application isn't often a serious worry.

In those cases, every byte counts. The size reduction caused by pruning is literally staggering. Their sample size for Dotfuscator isn't as mature as DashO's, but the results are looking similar. Pruned programs tend to run in less memory too. Dotfuscator allows significant customization features to allow the programmer to specify which types or methods are used dynamically.

The level of customization is as deep as you want to get. Virtually any. NET modules and it is impossible to round-trip such modules through Dotfuscator. If Dotfuscator detects such a module during loading, it will issue an error and stop processing.

Currently, only a small number of. I had a lot of questions and Bill Leach of Preemptive responded quickly with a number of suggestions. The Setup for this obfuscation assumes that you are using the DLL as a library referencing it from another, unobfuscated application , and is set to perform maximum obfuscation given that constraint.

This tells the renamer to leave exposed e. I also turned off the keepnamespace option, and specified a map file. With these settings in place, I ran the result through salamander and the results below. All of the more complicated receive the "Decompilation not complete" message. Those methods are littered with gotos that point to nonexistent labels. In at least one type DeflatorHuffman , the decompiler did not finish at all-- there was a message at the bottom "Decompilation failed" and not all methods showed up in the decompilation.

What this means is that the decompiler is graceful enough to not crash and burn when it can't decompile the code, but the results are generally not all that useful. Finally, this is a strong named assembly -- In my case, I need to remember to resign it after obfuscation or disable strong name verification for the assembly during testing. First, let's look at the Public exposed methods in my "helper" class - the ones that I had exposed to the COM interface. Note in red the methods that could not be decompiled correctly, and in blue the string obfiuscation:.

All rights reserved. Compression; using NZlib. Encryption; using System; using System. IO; using System. Net; using System. Finish ; deflaterOutputStream. Write bs1, 0, int bs1. Length ; stream. Read bs, 0, int bs. Concat str1, Encoding. Read bs1, 0, int bs1.