# Naming Convention

.NET Reactor offers various schemes of how your classes and members will be renamed during obfuscation.

# Debug

Debug adds the prefix 'Δ_' to the original names. This makes it easy to see which classes and members are renamed through obfuscation. For a diagnostic workflow, see Debugging.

Naming Convention Debug
Naming Convention Debug

# 'A' Overload

A-Overload replaces readable identifiers with repetitive sequences of visually similar Unicode variants of the letter A, such as À, Á, Â, Ã, Ä, and Å. The subtle differences between these characters make obfuscated names difficult to distinguish when browsing an assembly or reading decompiled code, making manual analysis more challenging.

Naming Convention 'A' Overload
Naming Convention 'A' Overload

# Incremental

If you want .NET Reactor always to generate the same obfuscation strings for your type and member names, you need to enable this option.

Naming Convention Incremental
Naming Convention Incremental

# Standard

This is the default scheme.

Naming Convention Default
Naming Convention Default

# Stealth

Generates random, meaningful names for obfuscated classes and members. This way it is less obvious which parts are obfuscated. For most cases 'Stealth' is the recommended option.

Naming Convention Stealth
Naming Convention Stealth

# Strange

Uses weird and displaced characters which confuse most decompiler code views. Only enable this feature if you don't want to use the protected assembly in a development environment(Visual Studio etc.).

Naming Convention Strange
Naming Convention Strange

# Unprintable Characters

Uses unprintable strings to obfuscate type and member names. Only enable this feature if you don't want to use the protected assembly in a development environment(Visual Studio etc.).

Naming Convention Unprintable
Naming Convention Unprintable

# Related topics

Obfuscation · Mapping File