...
AdiLock Enterprise Pro Edition

AdiLock User Manual

The AdiLock User Manual provides a comprehensive guide to installing, configuring, and using AdiLock Enterprise Pro Edition. This web-based manual presents the product documentation in a structured and easy-to-navigate format, allowing users to quickly find information about features, licensing, protection settings, and workflows. With organized sections, and step-by-step instructions, it helps developers and software vendors efficiently implement AdiLock to protect their applications and manage software licensing.

10 Core manual sections
3 Common workflows
128 Reserved feature slots
Showing all sections
Section 1

Introduction

AdiLock is a professional licensing and obfuscation platform for .NET developers and software vendors. It helps protect assemblies from reverse engineering, control who can run the software, and manage license entitlements from one interface.

What AdiLock Does

  • Code Obfuscation: Hardens assemblies against decompilation, tampering, and reverse engineering.
  • License Management: Generates cryptographically signed license files tied to hardware, time, or features.

Who This Manual Is For

Software developers and product managers distributing .NET applications commercially. No deep cryptography or compiler knowledge is required.

Section 2

Getting Started

Create a project first. A project stores protection settings, assembly paths, and feature definitions in one reusable file.

1
Launch AdiLock
The Dashboard opens automatically.
2
Create a new project
Use + New Project from the sidebar or File > New Project.
3
Select the primary assembly
Choose your .NET .exe or .dll and define an output directory.
4
Save the project
Your project name appears in the header and settings are available for future use.
Tip: Store the .nsp project file in a secure backup location. It contains the cryptographic keys used for protection and license generation.
Opening an existing project: Use Open Project from the Dashboard Quick Actions panel to restore all saved settings exactly as before.
Section 3

Dashboard

AdiLock Dashboard

The Dashboard provides a quick status overview of the active project and shortcuts for the most common tasks.

Last Build

Shows whether the most recent protection run is idle, in progress, or completed.

Protected Assemblies

Displays the number of configured assemblies in the current project.

Active Licenses

Shows how many license files have been generated for the project.

Quick Actions

Use Build Now, Open Project, and Save Project for fast access.

Section 4

Protection Settings

Protection Setting

Configure the security layers that will be applied during the build. Each setting can be toggled on or off.

Assembly Management

  • Primary Assembly: The main required .exe or .dll.
  • Secondary Assemblies: Optional dependent DLLs you also own.
  • Merge Assemblies: Combine secondary assemblies into one output file.

Recommended Baseline

Control Flow Guard, String Encryption, and Symbol Renaming create a strong default baseline for most commercial applications.

Protection Option What It Does Default
Control Flow Guard Restructures method logic to make source reconstruction harder. Enabled
String Encryption Encrypts hardcoded strings like URLs, API keys, and messages. Enabled
Anti-Tamper Checksum Adds self-verification and blocks execution when the file is modified. Optional
Symbol Renaming Replaces meaningful class, field, and method names with meaningless symbols. Enabled
Anti Debugging Detects debugger attachment and reacts based on configured behavior. Optional
Merge Assemblies Combines secondary assemblies into the primary output. Optional
IL Code Encryption Encrypts method bodies at the IL level and decrypts them only at runtime. Optional
Tip: For maximum protection, combine Control Flow Guard, Symbol Renaming, and IL Code Encryption.
Section 5

Build

Build Protection

The Build view executes the protection process and gives a real-time log of every step.

1
Review Protection Summary
Confirm the active settings match your intended release.
2
Start the build
Click START BUILD & PROTECT.
3
Watch the log
Follow the timestamped log on the right as each step completes.
4
Collect the protected assembly
When the completion message appears, use the configured output directory.
Before you build: Make sure the target assembly is not open in an IDE, decompiler, or debugger. Always keep a safe copy of the original unprotected assembly.
Section 6

Licensing

Licensing Management

Generate signed license files for customers. Licenses can be permanent, time-limited, trial-based, or tied to specific hardware.

License Types

  • Permanent: Never expires.
  • Trial: Valid for a limited number of days from first activation.
  • Term: Valid until a specific calendar date.

Hardware Binding

Use CPU, HDD, MotherBoard, BIOS, volume serial, MAC, and GPU selections to bind a license to a specific customer machine.

My Machine ID: The built-in Hardware ID Check tool lets users generate the exact hardware fingerprint required for licensing.
Tip: For high-value licenses, use at least three hardware components to make spoofing harder.
Section 7

Feature Management

Feature-Management Management

Feature Management lets you ship one protected binary and control product tiers through license-based feature flags.

Feature IDs

Every feature uses a stable reserved ID from FEAT-001 through FEAT-128, making runtime checks safe and predictable.

Adding a Feature

Click + Add, enter a feature name and optional description, mark it active if needed, then save it.

Editing & Deleting

Modify the name, description, or status from the detail panel. Delete carefully because existing licenses may rely on those definitions.

Saving UI State

Use Save UI State to persist feature definitions into the project file before closing the application.

Section 8

Common Workflows

Workflow A: Protect & Release

  1. Create or open the project and select the primary assembly.
  2. Enable the desired protection layers.
  3. Run the build and verify the output.
  4. Test the protected application before distribution.

Workflow B: Issue a License

  1. Collect the customer hardware ID.
  2. Choose the appropriate license type.
  3. Match the hardware components used in the fingerprint.
  4. Generate the .lic file and deliver it to the customer.

Workflow C: Tiered Features

  1. Define features such as Standard, Professional, or Export.
  2. Check feature IDs at runtime inside your application.
  3. Select the licensed features during license generation.
  4. Deliver the correct entitlement set to each customer tier.
Section 9

Troubleshooting

Common issues and practical fixes are collected here in an FAQ format.

Ensure the primary assembly is not locked by Visual Studio, a debugger, or a decompiler. Confirm the output folder exists and that AdiLock has write permission. Review the build log for the exact failing step.
Reflection-heavy systems may break when Symbol Renaming is enabled. Exclude the affected namespaces or types. If IL Code Encryption is active, temporarily disable it to isolate the issue.
Verify that the entered hardware ID exactly matches the customer machine output. Check the system clock for trial or term licenses. Confirm the .lic file is placed in the required location.
This usually means the project file was modified or lost. The embedded cryptographic keys inside the .nsp file are required to reproduce matching licenses.
Avoid deleting features in the middle of the list. Mark unused ones as inactive to preserve numbering consistency for application code.
Section 10

Tips & Best Practices

Protection

  • Use layered protection for better resilience.
  • Reserve IL Code Encryption for sensitive modules.
  • Run your full test suite against the protected build.

Licensing

  • Bind high-value licenses to at least three hardware components.
  • Plan a renewal grace period for term-based licensing.
  • Document the exact hardware components used for each license.

Project & File Management

  • Save the project file after each session.
  • Keep secure, versioned backups of the .nsp file.
  • Use clear project names with version numbers.

Feature Planning

  • Define anticipated features early to reserve stable IDs.
  • Write feature descriptions detailed enough for other team members.
Support

Support & Contact

If you need help beyond the manual, these support channels are available.

Account Representative

Enterprise customers can contact their dedicated account representative directly.

Audit Logs

The Audit Logs section in AdiLock provides a full history of builds and license generation activity.

Scroll to Top

Let's get in touch

Generic selectors
Exact matches only
Search in title
Search in content
Post Type Selectors

We’re Hear Your Business

Through Creativity, Integrity, and Innovations.

Seraphinite AcceleratorOptimized by Seraphinite Accelerator
Turns on site high speed to be attractive for people and search engines.