Search or filter the most common DN Shield questions below — protection layers, trial flow, licensing, and what to expect when shipping protected assemblies.
Anti-Debug adds runtime checks that detect debugger attachment and common inspection patterns. It's useful when you want to reduce easy step-through analysis of sensitive code paths.
Treat it as one layer in a stack, not a complete defense on its own.
It makes straightforward IL inspection and recovery less useful. Helpful when your assemblies ship to environments where casual disassembly is a real concern.
It restructures execution paths so logic is harder to follow in a decompiler. Useful for routines where readable branching would otherwise expose the real intent very quickly.
String encryption keeps sensitive literals, URLs, messages, and configuration values out of plain view in recovered assemblies — especially anything you don't want visible in a quick decompile.
Reserve it for higher-value routines where you want a stronger barrier than standard obfuscation alone. It increases protection depth around especially sensitive logic.
Anti-VM targets environments commonly used for analysis or detonation. It helps identify when 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 strip meaningful naming that makes recovered code easier to navigate.
The trial is intended for a single evaluation cycle per machine. It's HWID-locked, so reinstalling the OS or making major hardware changes may invalidate the environment.
After purchase, customers use their UID and registered email on the download page to access the latest build. That keeps repeat delivery straightforward without manual email handling.
Extensions keep updates, support, and compatibility improvements active. Useful when you want your protection workflow to stay current across future releases.
Use the support page and explain the situation. Mention hardware changes, test environments, or controlled lab evaluations so the request can be assessed properly.
If the FAQ doesn't cover your case, send a message with your UID, app type, and a short description so support can respond faster.
