SkillAgentSearch skills...

CSharpObfuscator

CSharp Obfuscator protects your .NET application code through obfuscation transforms, while maintaining debugging abilities for quality assurance testing.

Install / Use

/learn @nwtsolution/CSharpObfuscator
About this skill

Quality Score

0/100

Supported Platforms

Universal

README

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. obfuscation

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

string1

After

string2

string file

string3

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.

flow

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

Name | Value | Note -----|-------|----- MSBuildPath|path of MSBuild.exe|Specify the path if you have more than one MSBuild.exe installed Obfuscate|all|By default, all public declarations will not be obfuscated. Use this option to obfuscate all declarations. UseASCII|true|By default, declarations will be obfuscated with symbol characters. Use this option to obfuscate all declaration with ASCII characters. Reserve|comma separated word list| Reserved keywords ASCII|comma separated word list| Use ASCII characters for the matched declaration Suffix| any letter that is allowed to be used as a declaration name| The suffix of an obfuscated declaration.
Prefix| any letter that is allowed to be used as a declaration name| The prefix of an obfuscated declaration.
Reuse|true|Save the obfuscation result into a file (cso.db). Reuse the file for your next obfuscation. Extension| path of the extension assembly|Use the extension assembly to encrypt strings.

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

Name | Note -----|------- project| skip processing matched projects file:string| does not extract strings from matched files namespace| keep declarations within the matched namespace namespace:name| keep the namespace name only type| keep declarations within the matched type, it could be a class, enum or interface type:name| keep the type name only method| keep declaration within the matched method method:name| keep the method name only method:parameter| keep method parameters property| keep property variable| keep field variable enum:value| keep values of an enum any| comma separated word, does not support wildcard

View on GitHub
GitHub Stars49
CategoryDevelopment
Updated2mo ago
Forks10

Languages

C#

Security Score

80/100

Audited on Jan 12, 2026

No findings