.NET licensing: hiding the validator isn’t the same as protecting the entitlementA question for people shipping paid .NET desktop apps: when you protect your licensing code, are you protecting the validator-or the entire path that enables paid features? Those aren’t necessarily th4 min read·rustemsoft.hashnode.dev1d ago
Obfuscating .NET 11 Without Breaking Reflection: A Small-App WalkthroughA developer-focused approach to protecting implementation details while preserving the names your application actually needs. Consider this hypothetical bug report: “The protected application starts8 min read·rustemsoft.hashnode.dev3d ago
I Finally Stopped Shipping Unprotected DLLsA practical guide to wiring Opaquer into Visual Studio post-build events — including the three gotchas that cost me the most time By Rustemsoft LLC · September 2026 TL;DR I got tired of remembering to8 min read·rustemsoft.hashnode.devNov 9
Moving strings out of the managed assembly: worth it, and what are the trade-offs?1. Hardcoded strings in .NET builds: what a decompiler shows, and what actually helps. 2. Moving strings out of the managed assembly.3 min read·rustemsoft.hashnode.devNov 2
How to Debug Obfuscated .NET Applications: Using Rename Maps to Recover Production Stack TracesWhy reproducible .NET obfuscation matters: deterministic builds, strong-name signing, rename maps, and CI/CD practices.12 min read·rustemsoft.hashnode.devOct 25