Symbol Renaming

Performance: None 🔐Potency: High 🧠Resilience: High

Understanding the protection

Symbol renaming is a critical obfuscation technique, the names of classes, methods, properties, fields, method parameters, and locals are replaced with randomly generated names.

Before Obfuscation:

public static void MyMethod(string parameter)

After Obfuscation:

public static void _[[](___])(_(string __)())_)

Tuning the protection for best performance

There are three different modes for this protection, all of them serve the same purpose, erasing the original names of your application, however, depending on the aim that you want to achieve with the obfuscation, you should opt which one suits you better.

Minify

When choosing this option, the names of your application are removed to ensure that your application size is the smallest possible, when erasing the data is not possible, the obfuscator will use single characters as names for the member being renamed.

Before:

public static void MyMethod(string parameter)

After:

public static void (string )

Encrypted

When choosing this option, the names of your application are encrypted with a private key of your preference, this makes it possible for you to decode stacktraces provided by customers and easily debug your application after obfuscation.

Before:

public static void MyMethod(string parameter)

After:

public static void MTc4OTI0NTYxNw==(string MTc4OTI0NTYxNw==)

Default

When choosing this option, the names of your application become incredibly difficult to read both to humans and machines, leading to the crash of reverse engineering applications in some scenarios.

Before:

public static void MyMethod(string parameter)

After:

public static void _[[](___])(_(string __)())_)

Last updated

Was this helpful?