Series
A practical series exploring how modern .NET applications are protected in real-world environments. Topics include obfuscation, anti-tamper techniques, licensing, reverse-engineering resistance, deterministic builds, CI/CD integration, strong-name signing, and production diagnostics. The focus is on understanding both the security and operational aspects of application protection, with examples, pitfalls, and lessons learned from real projects.
Discussion: how do you handle endpoints and tokens that have to ship in a desktop .NET app? Disclosure: I'm affiliated with Rustemsoft, the company behind Skater .NET Obfuscator, which I mention below
Obfuscation helps protect .NET applications against reverse engineering, but it introduces a practical challenge: when a production application crashes, the stack trace may no longer contain the origi
