One of the advantages of the .NET architecture is that assemblies built with it contain lots of useful information that can be recovered using ILDASM, the intermediate language disassembler. A side effect, though, is that someone with access to your binaries can recover a good approximation of the original source code. Skater .NET obfuscator implements obfuscation that is accomplished using a set of related technologies. Its goal is to hide the intent of a program without changing its runtime behavior. It is not encryption, but in the context of .NET code, it might be better. Obfuscation is a process that is applied to compiled .NET assemblies, not source code. Skater .NET obfuscator never reads or alters your source code. Obfuscation encrypts the source code and removes some unnecessary information from the assembly metadata when it deems that it is safe to do so, thus making the assembly more difficult to understand or read after it is decompiled. The assembly metadata and manifest are used by the dissemblers to decompile them and get the original source code. Note that even if an application is compiled to native code at the time of execution, the Microsoft .NET runtime environment still requires that the assembly metadata and IL code be embedded in an assembly before it starts its execution. There are a number of Skater .NET obfuscator’s techniques that can be used to obfuscate. Obfuscation never changes your source code. Rather, the Skater obfuscates your assemblies using a specific encryption methodology and transforms them into another assembly that is obfuscated, but the functionality of it remains unaltered. You do not need to let hackers use the handy ILDASM utility on your app for questionable purposes. You can protect your code with Skater .NET obfuscator. Obfuscation raises the reverse engineering bar.