Menu

Obfuscating a ClickOnce-Deployed App: Why Order of Operations Decides Whether It Even Launches
πŸ“°

Obfuscating a ClickOnce-Deployed App: Why Order of Operations Decides Whether It Even Launches

DEV Community: dotnetΒ·Zero HeartbeatΒ·5 days ago
#O3GG5lx9
#devtodotnet#devto#dev#clickonce#obfuscation
Reading 0:00
15s threshold

There is a particular way a ClickOnce app fails after you add obfuscation that sends people down entirely the wrong rabbit hole: the app installs fine, then refuses to launch with a file validation or hash-mismatch error, and nothing in your code changed. The instinct is to suspect the obfuscator broke the assembly. It did not. ClickOnce is doing exactly what it is designed to do β€” refusing to run a file whose bytes do not match the hash it recorded β€” and the real bug is the order in which your build steps ran. Get the order right and obfuscation and ClickOnce coexist with no drama.

Why ClickOnce is unusually sensitive

Most deployment mechanisms copy files and run them. ClickOnce does more: its application manifest records, for every file in the deployment, a cryptographic hash and a size, and the ClickOnce runtime verifies each file against that record before launching.…

Continue reading β€” create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.