Contents 

Introduction
Welcome
Features
System Requirements
User Interface
Overview
The Main Menu
The Main Panel
The Tasks Panel
GUI Elements
Addtional Files
Additional License Information
License File Settings
License Manager
Main Assembly
Master Key
Licensing System
Understanding The License System
How Locks Work
Hardware Identity Specific Licensing
SDK
General Information
License.dll
LicenseGen.dll
StackTraceDeobfuscator.dll
Definitions
Anti ILDASM
Anti Tampering
Compress & Encrypt Resources
Control Flow Obfuscation
Embed Assemblies
EvaluationLock
HardwareLock
License File
Mapping File
Merge Assemblies
Native EXE File
NecroBit
Obfuscation
Pre-JIT Methods
String Encryption
Tools
Hardware ID Tool Generator
License Examiner Tool
License Invalidation Tool
License Reactivation Tool
Stack Trace Deobfuscator
ShareIt Module Generator
Testing
Library - Test Environment
Examples
Protect An Assembly
Lock An Assembly
Unlock An Locked Assembly
Ordering
Register Online
License Agreement
Why register?
Support and Contact
Technical Support
Contact
Command Line Parameters

.NET Reactor Online Help

Prev Page Next Page
Understanding the .NET Reactor License System
 

.NET Reactor's pre-built licensing system observes high security standards, and in prevalent cases will fulfill or exceed the proprietary security and convenience your enterprise might develop at considerable expense or difficulty.

Most needs will be met by simply deploying hardware identity locks. Nonetheless, the .NET Reactor License System is designed to readily fit practically any further need or automation.

If you deploy our prebuilt system with hardware (machine specific) license locks, licensing of initial product releases can readily be handled manually with .NET Reactor itself at a clip of about a minute per license — allowing you to release protected wares just minutes after purchasing .NET Reactor. Later (if you want), practically any desirable degree of automation can be integrated by way of the .NET Reactor Software Development Kit (SDK).

You can deploy independent, proprietary license enforcement. Or you can rely on .NET Reactor's prebuilt license enforcement system to any degree you desire. You can pursue two basic licensing paths — prebuilt licensing, or extended (customized) proprietary licensing. The latter can build upon our prebuilt hardware identifying system, or it can integrate proprietary processes with information you can embed in our binary license files. In either approach, prebuilt .NET Reactor processes make it easier to produce secure, inviolable licensing systems than native .NET SDKs.

A critical security feature of this system is that in no way and at no time does any code exist outside your premises which is necessary to determining valid licenses. .NET Reactor's binary licensing system is exceedingly secure.



License System
(Hardware identity lock is optional)

   
Converted from CHM to HTML with chm2web Pro 2.85 (unicode)