Search or filter the most common DN Shield questions below. The FAQ covers protection layers, trial flow, licensing, and what to expect when shipping protected assemblies.
Anti Debug adds runtime checks that can detect debugger attachment or common inspection patterns. It is useful when you want to reduce easy step-through analysis of sensitive code paths.
It is best viewed as one layer in a stack rather than a complete defense on its own.
It is intended to make straightforward IL inspection and recovery less useful. That helps when your assemblies are distributed to environments where casual disassembly is a concern.
Control-flow obfuscation restructures execution paths so logic is harder to follow in a decompiler. It is useful for routines where readable branching would otherwise expose the real intent very quickly.
String encryption helps keep sensitive literals, URLs, messages, and configuration values out of plain view in recovered assemblies. It is especially useful for anything you do not want visible in a quick decompile.
Virtualization is best reserved for higher-value routines where you want a stronger barrier than standard obfuscation alone. It can increase protection depth around especially sensitive logic.
Anti VM features are aimed at environments commonly used for analysis or detonation. They can help identify cases where a build is being inspected in a controlled sandbox or virtual machine.
DN Shield can rename types, methods, properties, parameters, events, and fields. The goal is to remove meaningful naming that makes recovered code easier to navigate and understand.
The trial is intended for a single evaluation cycle per machine. It is HWID-locked, so reinstalling the OS or making major hardware changes may invalidate the evaluation environment.
After purchase, customers can use their UID and registered email to access the latest build from the download page. That keeps repeat delivery straightforward without requiring manual email handling every time.
Extensions keep updates, support, and compatibility improvements active. They are useful when you want your protection workflow to stay current across future releases.
Use the support page and explain the situation. Include whether the request is for hardware changes, a test environment, or a controlled lab evaluation so the request can be assessed properly.
If the FAQ does not cover your case, send a message with your UID, app type, and a short description of the issue so support can respond faster.