Desktop GUI

The desktop GUI is the easiest way to protect an assembly and to see exactly what each option does. Launch Nebula.NET from the Start menu.

Create or open a project

Start a new project with the wizard — name it, add the assemblies to protect, and pick an output folder — or open an existing project. Settings are saved as a .nebproj file you can reopen later. Opening a project analyzes its assemblies; while that runs you’ll see a busy cursor, and large projects (tens of assemblies) take a few seconds.

The workspace

The editor is organized into tabs (the selected tab is highlighted so it’s easy to switch between them):

• Assemblies — add / remove / clear the .dll / .exe files to protect (drag-and-drop works too). Select one or more and press Remove (or Delete) to drop them.
• Selection — the assembly tree, where you choose exactly what to transform (see below).
• Protection options — run-wide transforms: string encryption, control-flow (with intensity), anti-tamper, anti-debug, resource/method encryption, metadata hardening.
• Output & signing — the output directory and strong-name / Authenticode signing.
• Activity log — streamed output of each run.

Choosing what to protect

The Selection tree shows each assembly → namespace → type → method → string, with three per-item toggles:

• R — rename this identifier
• C — control-flow-obfuscate this method
• S — encrypt this string

Key behaviors:

• Nothing is selected by default. You opt in to what you want, at any level. Ticking a node cascades to everything under it (a three-state box shows partial selection), so you can select a whole assembly, a namespace, a single type or method, or an individual string.
• Filter by namespace, class, method or string using the box above the tree to jump to what you need; it’s debounced so it stays responsive on large inputs.
• Expand / collapse to drill in. The node you expand, collapse or click becomes the single selected node and stays in view.
• Prefer to keep your public API intact? Turn on Preserve public API in the options — then only internal/private members are renamed regardless of selection. See Keeping your app working.

Very large projects: for an extreme, string-heavy input the tree caps how many individual string entries it lists (so it stays fast); type/method selection is never capped. When that happens the Activity log says so — use the config’s encryptStrings / encryptStringsInclude for full string coverage, or the CLI for the biggest products.

Run

Click Obfuscate. The Activity log opens and streams progress; when it finishes, your protected assemblies are in the output folder. Always run your own tests against the protected build.

Register a license

Click Register, paste your license key and confirm to unlock the full edition. The edition in effect (FREE / PRO / ENTERPRISE) is shown in the title bar and the About box. See Licensing & activation.