# .NET Reactor Documentation

Protect your assemblies, configure licensing, and integrate .NET Reactor into your build workflow.

Protect your first assembly Explore the features

# Choose your next step

Protect your software

Configure licensing

Start with a guided example, then explore the available protection options.

Protect an assembly

Understand protection features

Learn how locks and license files work before configuring your licensing workflow.

Understand the licensing system

Lock an assembly

Automate your builds

Work with the SDK

Connect .NET Reactor to your build process and find the command-line reference.

Build Integration Manager

Command-line parameters

Explore the SDK documentation and the examples for working with license information.

License.dll examples

# Find a solution

# Publish and package your application

What are you working on?	Open this guide
Preparing a protected release	Publish and distribute protected applications
A protected single-file executable	Obfuscate and publish a single-file application
ReadyToRun publishing	Using ReadyToRun
Merging, embedding, or bundling dependencies	Merge vs. Embed vs. Single-File Bundling
Strong names and publisher signatures	Code signing in an obfuscated build

# Automate and verify a release

What are you working on?	Open this guide
GitHub Actions	Protect a release with GitHub Actions
Azure DevOps Pipelines	Protect a release with Azure DevOps
Checking the files customers receive	Verify that your published application is protected
Balancing protection, compatibility, and runtime cost	Choose protection settings
Inspecting renamed code during diagnosis	Debug protected applications
Reading an obfuscated error report	Debug stack traces with mapping files

# Preserve compatibility and diagnose failures

What are you working on?	Open this guide
dotPeek still displays the original source	Check the actual decompiler output
A reusable DLL or NuGet package	Protect a library without breaking its public API
Reflection and renamed members	Obfuscation and Reflection
Public names across related assemblies	Cross-Assembly Obfuscation
A protected application does not start	Diagnose startup problems
JSON, XML, or persisted data breaks after obfuscation	Serialization and Obfuscation
Problems after trimming	Trimming Problems
Antivirus detections	Investigate a suspected false positive

# License your software

What are you working on?	Open this guide
Creating and delivering customer license files	Create License Files
An evaluation version that upgrades through a license	Create a trial version

# Reference and support

Use the user interface overview to find a setting, or check the system requirements.

If .NET Reactor itself cannot be activated, see Activation Troubleshooting. For issues that are not covered here, see Technical Support.