Awesome

CSharp Obfuscator

CSharp Obfuscator protects your .NET application code through obfuscation transforms, while maintaining debugging abilities for quality assurance testing. This is made possible by the Roslyn open source project.

Features

Renaming

Rename obfuscation applies trivial names, as short as a single character, to methods, variables, classes, and fields that allow code readability.

Scrambling Strings

CSharp Obfuscator extracts all strings and puts them in a seperate source file. All strings are serialized and encoded, which blocks the hacker from locating the critical method by searching for keyword strings. For further protection, you can encrypt the strings using your unique key.

Before

After

string file

Encrypt strings with an extension DLL

• Download the extension project
• Implement the encryption in the EncodeStringArray method
• Return the full name of the decryption method that exists in your project/solution
• Build the project and set the file path in the configuration file

Integrate with the existing development cycle

CSharp Obfuscator obfuscates your source code, so you can run full quality assurance tests even after your source code has been obfuscated, ensuring that your code is both tested and protected. It will also update Xamarin XAML files with the obfuscated code.

It can be seamlessly integrated with the exising development cycle when each c# project only targets one framework. If a c# project targets multiple framework, you need obfuscate the project for each framework seperately.

Versions

Both free and premium versions are available. Please check NorWest Solution for details.

Command Line

Usage: cso.exe [MSBuild options] [Options]
    
MSBuild options: the same options when you use MSBuild.exe to build your solution.

Options:
-activate:account={account};sn={sn}        Activate your license
-deactivate                                Deactivate your license
-config:{file}                             A file containing the obfuscation configuration and rules

Obfuscation Configuration File

• A text file that contains the obfuscation configuration and rules.
• Each configuration rule should be on a separate line.
• Any lines starting with a hash symbol (#) will be ignored.

Configuration

Rules

Use rules to skip the obfuscation of matched declarations. Use the following format to define a rule:

keep {type} {pattern}

A pattern should be the fullname of a declaration and can use an asterisk (*) as the wildcard, such as

keep namespace *.Tests

Available rules