An error occurred during search results load.
Eazfuscator.NET provides a simple integration path with Visual Studio projects, as shown in the Quick Start guide.
The provided integration is light yet powerful. What it essentially does is register Eazfuscator.NET in the post-build event of the project:
For some project types, Eazfuscator.NET is integrated at MSBuild level:
<Project Sdk="Microsoft.NET.Sdk"> <Import Condition=" '$(EAZFUSCATOR_NET_HOME)' != '' and Exists('$(EAZFUSCATOR_NET_HOME)\Integration\MSBuild\Eazfuscator.NET.targets') " Project="$(EAZFUSCATOR_NET_HOME)\Integration\MSBuild\Eazfuscator.NET.targets" /> <PropertyGroup> <OutputType>Exe</OutputType> <TargetFramework>net5.0</TargetFramework> </PropertyGroup> <PropertyGroup> <EazfuscatorIntegration>MSBuild</EazfuscatorIntegration> <EazfuscatorActiveConfiguration>Release</EazfuscatorActiveConfiguration> <EazfuscatorCompatibilityVersion>2020.4</EazfuscatorCompatibilityVersion> </PropertyGroup> </Project>
The import directive instructs MSBuild to import Eazfuscator.NET targets.
A group of Eazfuscator.NET MSBuild properties configures the obfuscation integration.
Once registered, Eazfuscator.NET comes into action and obfuscates the assembly
every time the project is built in
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 experiences Eazfuscator.NET for the first time:
The general answer to these questions: it just works, and there is no need to worry about it; just give it a try.