Protecting a headless .NET Worker Service
A .NET Worker Service is the easiest kind of app to obfuscate aggressively and the easiest to forget to obfuscate at all. It ships to a customer''s server as a DLL, runs headless as a Windows Service or a systemd unit, and carries your integration secrets and your business logic with almost no reflection surface to protect — which means you can rename nearly everything. This post covers why a background worker is a tempting reverse-engineering target, the handful of Generic Host seams that still read names (options binding, assembly scanning, serialized DTOs), and how to wire Nebula.NET into the publish step so the shipped binary is renamed, string-encrypted and virtualized where it counts.






