Support
Stuck, found a bug, or have a billing question? We answer every message.
Contact us
Email [email protected] and we'll get back to you — Pro subscribers are answered first.
Billing questions: include the email address on your account. We never need your password or your card details — payment is handled entirely by Stripe, and most billing changes are self-serve from your account page.
Reporting an obfuscation problem
The fastest reports to act on include:
- What you uploaded — target framework, roughly what the assembly is.
- What happened: an error message, or how the output misbehaves.
- Whether the original assembly runs correctly.
- For runtime breaks: whether the app uses reflection, serialization, XAML, or convention-based DI — the usual suspects.
Before you write — quick answers
"Obfuscation failed"
Usually a native binary, NativeAOT publish, or an already-protected assembly.
App breaks after obfuscation
Almost always a by-name lookup at runtime. The FAQ lists each cause and fix.
Cancelling or billing
Self-serve from your account via the Stripe portal — no email needed.
MyApp.exe or MyApp.dll?
On modern .NET, upload the .dll — the .exe is just a native launcher.