--- title: "#nebulanet articles | Hashnode" description: "Explore 44 articles tagged #nebulanet on Hashnode. Tutorials, guides, and how-tos from the community." url: "https://hashnode.com/tag/nebulanet" --- Tag # #nebulanet 44 posts · 0 followers [Zero Heartbeat](https://hashnode.com/@clustron) · [1d ago](https://hashnode.com/posts/which-nebulanet-edition-is-right-for-you/6af328cf65dfe6eeccc36ce3) ### [Which Nebula.NET edition is right for you?](https://delta1labs.hashnode.dev/which-nebulanet-edition-is-right-for-you?utm_source=hashnode&utm_medium=feed) Nebula.NET comes in three editions — Free, Licensed, and Enterprise. They're all built on the same tested engine; the difference is how much protection, automation, and support you get. Here's how to 3 min read · [delta1labs.hashnode.dev](https://delta1labs.hashnode.dev/which-nebulanet-edition-is-right-for-you?utm_source=hashnode&utm_medium=feed) [Zero Heartbeat](https://hashnode.com/@clustron) · [1d ago](https://hashnode.com/posts/did-your-obfuscation-actually-work-check-it-in-glassnet/6af328cb31aa73066ff0a6fe) ### [Did your obfuscation actually work? Check it in Glass.NET](https://delta1labs.hashnode.dev/did-your-obfuscation-actually-work-check-it-in-glassnet?utm_source=hashnode&utm_medium=feed) You ran your obfuscator. The build succeeded, the tests are green, the package is signed. So your code is protected now — right? Maybe. A successful build tells you the obfuscator didn't crash. It tel 7 min read · [delta1labs.hashnode.dev](https://delta1labs.hashnode.dev/did-your-obfuscation-actually-work-check-it-in-glassnet?utm_source=hashnode&utm_medium=feed) [Zero Heartbeat](https://hashnode.com/@clustron) · [1d ago](https://hashnode.com/posts/string-encryption-in-net-where-the-key-hides-and-why-it-matters/6af328c131aa73066ff09546) ### [String encryption in .NET: where the key hides and why it matters](https://delta1labs.hashnode.dev/string-encryption-in-net-where-the-key-hides-and-why-it-matters?utm_source=hashnode&utm_medium=feed) Every .NET assembly leaks its string literals. Run strings over a DLL, or open it in any decompiler, and the connection strings, API endpoints, licence-check messages, feature flags and SQL are all si 7 min read · [delta1labs.hashnode.dev](https://delta1labs.hashnode.dev/string-encryption-in-net-where-the-key-hides-and-why-it-matters?utm_source=hashnode&utm_medium=feed) [Zero Heartbeat](https://hashnode.com/@clustron) · [1d ago](https://hashnode.com/posts/keeping-obfuscated-names-stable-across-releases-with-nebulas-seed-map/6af328b931aa73066ff08b35) ### [Keeping obfuscated names stable across releases with Nebula''s seed map](https://delta1labs.hashnode.dev/keeping-obfuscated-names-stable-across-releases-with-nebulas-seed-map?utm_source=hashnode&utm_medium=feed) Ship an obfuscated .NET build and you get a mapping: MyApp.Billing.Invoice.Recalculate became n.a.b, and you tuck away the map so you can decode the crash reports that will arrive. Ship 1.4.1 a week l 7 min read · [delta1labs.hashnode.dev](https://delta1labs.hashnode.dev/keeping-obfuscated-names-stable-across-releases-with-nebulas-seed-map?utm_source=hashnode&utm_medium=feed) [Zero Heartbeat](https://hashnode.com/@clustron) · [1d ago](https://hashnode.com/posts/renaming-to-collisions-how-nebula-reuses-one-name-across-members-and-why-the-clr-tells-them-apart-by/6af328a9ef86d93b24223cd1) ### [Renaming to collisions: how Nebula reuses one name across members, and why the CLR tells them apart by signature](https://delta1labs.hashnode.dev/renaming-to-collisions-how-nebula-reuses-one-name-across-members-and-why-the-clr-tells-them-apart-by?utm_source=hashnode&utm_medium=feed) Most people picture renaming as a dictionary: every identifier gets its own fresh, meaningless replacement. CalculateTax becomes a, ValidateLicense becomes b, \_cachedResult becomes c, and so on down t 8 min read · [delta1labs.hashnode.dev](https://delta1labs.hashnode.dev/renaming-to-collisions-how-nebula-reuses-one-name-across-members-and-why-the-clr-tells-them-apart-by?utm_source=hashnode&utm_medium=feed) [Zero Heartbeat](https://hashnode.com/@clustron) · [1d ago](https://hashnode.com/posts/re-signing-a-net-assembly-after-obfuscation-strong-names-and-authenticode/6af328a331aa73066ff0679d) ### [Re-signing a .NET assembly after obfuscation: strong names and Authenticode](https://delta1labs.hashnode.dev/re-signing-a-net-assembly-after-obfuscation-strong-names-and-authenticode?utm_source=hashnode&utm_medium=feed) Signing and obfuscation have an ordering problem that bites every team the first time they turn on protection in a release pipeline. Both a strong name and an Authenticode signature are signatures ove 7 min read · [delta1labs.hashnode.dev](https://delta1labs.hashnode.dev/re-signing-a-net-assembly-after-obfuscation-strong-names-and-authenticode?utm_source=hashnode&utm_medium=feed) [Zero Heartbeat](https://hashnode.com/@clustron) · [1d ago](https://hashnode.com/posts/how-to-protect-a-blazor-webassembly-app-from-decompilation/6af3289a74474d83e1774ff5) ### [How to protect a Blazor WebAssembly app from decompilation](https://delta1labs.hashnode.dev/how-to-protect-a-blazor-webassembly-app-from-decompilation?utm_source=hashnode&utm_medium=feed) Blazor WebAssembly is a genuinely great way to write a .NET SPA. It's also the single most exposed target you can ship .NET to — and most obfuscators quietly ignore it. If you have proprietary logic, 4 min read · [delta1labs.hashnode.dev](https://delta1labs.hashnode.dev/how-to-protect-a-blazor-webassembly-app-from-decompilation?utm_source=hashnode&utm_medium=feed) [Zero Heartbeat](https://hashnode.com/@clustron) · [1d ago](https://hashnode.com/posts/obfuscating-a-winforms-app-without-losing-your-designer-resources/6af3288c4d349388ef339d72) ### [Obfuscating a WinForms app without losing your designer resources](https://delta1labs.hashnode.dev/obfuscating-a-winforms-app-without-losing-your-designer-resources?utm_source=hashnode&utm_medium=feed) If you have obfuscated a WPF app you already know the one rule there: XAML binds to view-model members by name, so those names have to survive. WinForms looks similar — a desktop app, a .Designer.cs f 7 min read · [delta1labs.hashnode.dev](https://delta1labs.hashnode.dev/obfuscating-a-winforms-app-without-losing-your-designer-resources?utm_source=hashnode&utm_medium=feed) [Zero Heartbeat](https://hashnode.com/@clustron) · [1d ago](https://hashnode.com/posts/obfuscating-virtual-and-interface-members-override-chains-explicit-implementations-and-the-methodimp/6af3288a31aa73066ff040e1) ### [Obfuscating virtual and interface members: override chains, explicit implementations, and the MethodImpl table that ties them together](https://delta1labs.hashnode.dev/obfuscating-virtual-and-interface-members-override-chains-explicit-implementations-and-the-methodimp?utm_source=hashnode&utm_medium=feed) Rename a private helper and you have edited one string in the #Strings heap; nothing else in the assembly cares. Rename a virtual method and you have reached into the mechanism the runtime uses to dec 13 min read · [delta1labs.hashnode.dev](https://delta1labs.hashnode.dev/obfuscating-virtual-and-interface-members-override-chains-explicit-implementations-and-the-methodimp?utm_source=hashnode&utm_medium=feed) [Zero Heartbeat](https://hashnode.com/@clustron) · [1d ago](https://hashnode.com/posts/obfuscating-a-type-you-serialize-with-systemtextjson-jsonpropertyname-is-the-contract-the-renamed-pr/6af3288774474d83e177102d) ### [Obfuscating a type you serialize with System.Text.Json: \[JsonPropertyName\] is the contract, the renamed property is not](https://delta1labs.hashnode.dev/obfuscating-a-type-you-serialize-with-systemtextjson-jsonpropertyname-is-the-contract-the-renamed-pr?utm_source=hashnode&utm_medium=feed) Here is a type that works perfectly until the day you obfuscate it: public sealed class Order { public string Customer { get; set; } = ""; public decimal Total { get; set; } public DateTim 9 min read · [delta1labs.hashnode.dev](https://delta1labs.hashnode.dev/obfuscating-a-type-you-serialize-with-systemtextjson-jsonpropertyname-is-the-contract-the-renamed-pr?utm_source=hashnode&utm_medium=feed)