- Table of Contents
- What Is Eazfuscator.NET?
- Introduction
- Quick Start
- How Does Eazfuscator.NET Work?
- Advanced Features
- About Advanced Features
- Declarative Obfuscation Using Custom Attributes
- Conditional Obfuscation
- Symbol Names Encryption
- Advanced Symbol Renaming Options
- Advanced String Encryption Options
- Code Control Flow Obfuscation
- Assemblies Merging
- Assemblies Embedding
- Resource Encryption
- Serialization Tuning
- Debugging
- PEVerify Integration
- Probing Paths
- Script Variables
- Sensei Features
- Virtualization
- Troubleshooting
- Best Practices
- Deployment
- Glossary
- Bibliography
Sorry
An error occurred during search results load.
Eazfuscator.NET provides a simple integration path with Visual Studio projects as shown in Quick Start guide.
The provided integration is light yet powerful. What it essentially does is register Eazfuscator.NET in post-build event of the project:
Once registered, Eazfuscator.NET comes into action and obfuscates the assembly
every time the project is built in Release configuration.
Eazfuscator.NET messages can be found at Output Window of Visual Studio with → (Ctrl+W,O):
That's it. The rest of the things just work.
The paralysis of simplicity is a problem that may apply to a person who experience Eazfuscator.NET for the first time:
- “How does Eazfuscator.NET know which key to use for the assembly signing?”
- “How is it possible it just works everytime?”
- “What should I do to make Eazfuscator.NET work with MSBuild?”
- and so on.
The general answer to these questions: it just works and there is no need to worry about it; just give it a try.