---
title: "#guide articles | Hashnode"
description: "Explore 1,950 articles tagged #guide on Hashnode. Tutorials, guides, and how-tos from the community."
url: "https://hashnode.com/tag/guide"
---

Tag

# #guide

1,950 posts · 35 followers

[Zero Heartbeat](https://hashnode.com/@clustron) · [5d ago](https://hashnode.com/posts/obfuscating-a-net-global-tool-without-breaking-commands/6af699a05483fe3c6285c2d5)

### [Obfuscating a .NET global tool without breaking commands](https://delta1labs.hashnode.dev/obfuscating-a-net-global-tool-without-breaking-commands?utm_source=hashnode&utm_medium=feed)

A .NET global tool — a console app you dotnet pack with PackAsTool and install with dotnet tool install -g — is one of the easier things to protect, for a reason that is worth understanding before you

8 min read · [delta1labs.hashnode.dev](https://delta1labs.hashnode.dev/obfuscating-a-net-global-tool-without-breaking-commands?utm_source=hashnode&utm_medium=feed)

[Zero Heartbeat](https://hashnode.com/@clustron) · [Nov 11](https://hashnode.com/posts/licensing-software-on-ephemeral-ci-and-cloud-build-agents/6af4094e2bd71c8cc86a6d73)

### [Licensing software on ephemeral CI and cloud build agents](https://delta1labs.hashnode.dev/licensing-software-on-ephemeral-ci-and-cloud-build-agents?utm_source=hashnode&utm_medium=feed)

Licensing models were mostly designed for machines that stay put — a desktop, a server, a workstation. CI and cloud build agents violate that assumption on purpose: they exist for the duration of one

4 min read · [delta1labs.hashnode.dev](https://delta1labs.hashnode.dev/licensing-software-on-ephemeral-ci-and-cloud-build-agents?utm_source=hashnode&utm_medium=feed)

[Zero Heartbeat](https://hashnode.com/@clustron) · [Nov 11](https://hashnode.com/posts/how-p-invoke-and-dllimport-decompile/6af408b5251d5dfedd3cb24c)

### [How P/Invoke and DllImport decompile](https://delta1labs.hashnode.dev/how-p-invoke-and-dllimport-decompile?utm_source=hashnode&utm_medium=feed)

When you need to understand what an unfamiliar .NET assembly actually does — not to its own data, but to the machine — the native interop is where the answer lives. Managed code that stays inside the

4 min read · [delta1labs.hashnode.dev](https://delta1labs.hashnode.dev/how-p-invoke-and-dllimport-decompile?utm_source=hashnode&utm_medium=feed)

[Zero Heartbeat](https://hashnode.com/@clustron) · [Nov 11](https://hashnode.com/posts/letting-partners-provision-license-keys-safely/6af4072b251d5dfedd3795b5)

### [Letting partners provision license keys safely](https://delta1labs.hashnode.dev/letting-partners-provision-license-keys-safely?utm_source=hashnode&utm_medium=feed)

Direct licensing has one issuer: you. OEM, white-label, and reseller channels break that assumption — now partners issue keys to their customers, under their brand, on their schedule, and you are not

5 min read · [delta1labs.hashnode.dev](https://delta1labs.hashnode.dev/letting-partners-provision-license-keys-safely?utm_source=hashnode&utm_medium=feed)

[Zero Heartbeat](https://hashnode.com/@clustron) · [Nov 11](https://hashnode.com/posts/obfuscating-a-clickonce-app-without-breaking-launch/6af406e5d74b6f0a8ac80c04)

### [Obfuscating a ClickOnce app without breaking launch](https://delta1labs.hashnode.dev/obfuscating-a-clickonce-app-without-breaking-launch?utm_source=hashnode&utm_medium=feed)

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

4 min read · [delta1labs.hashnode.dev](https://delta1labs.hashnode.dev/obfuscating-a-clickonce-app-without-breaking-launch?utm_source=hashnode&utm_medium=feed)

[Zero Heartbeat](https://hashnode.com/@clustron) · [Nov 11](https://hashnode.com/posts/obfuscating-code-that-generates-code-at-runtime/6af4045e6bc1d9a6bce6cb67)

### [Obfuscating code that generates code at runtime](https://delta1labs.hashnode.dev/obfuscating-code-that-generates-code-at-runtime?utm_source=hashnode&utm_medium=feed)

Serializers, ORMs, DI containers, mappers, and rule engines all do the same trick under the hood: they write IL at runtime instead of calling your methods directly, because a generated, specialised me

5 min read · [delta1labs.hashnode.dev](https://delta1labs.hashnode.dev/obfuscating-code-that-generates-code-at-runtime?utm_source=hashnode&utm_medium=feed)

[Zero Heartbeat](https://hashnode.com/@clustron) · [Nov 11](https://hashnode.com/posts/keeping-license-activation-across-desktop-auto-updates/6af403ec936535f226c9fcfa)

### [Keeping license activation across desktop auto-updates](https://delta1labs.hashnode.dev/keeping-license-activation-across-desktop-auto-updates?utm_source=hashnode&utm_medium=feed)

You added licensing, activation works, everyone is happy — and then you ship your first auto-update and the support tickets start: "it's asking me to activate again." The cause is almost always the sa

4 min read · [delta1labs.hashnode.dev](https://delta1labs.hashnode.dev/keeping-license-activation-across-desktop-auto-updates?utm_source=hashnode&utm_medium=feed)

[Zero Heartbeat](https://hashnode.com/@clustron) · [Nov 11](https://hashnode.com/posts/why-readytorun-assemblies-still-decompile-cleanly/6af4035f12662e205ff2288b)

### [Why ReadyToRun assemblies still decompile cleanly](https://delta1labs.hashnode.dev/why-readytorun-assemblies-still-decompile-cleanly?utm_source=hashnode&utm_medium=feed)

If you have ever been handed a "precompiled" .NET assembly and assumed a decompiler would choke on it, ReadyToRun is the happy surprise. R2R is how .NET ships fast-starting code — the runtime librarie

4 min read · [delta1labs.hashnode.dev](https://delta1labs.hashnode.dev/why-readytorun-assemblies-still-decompile-cleanly?utm_source=hashnode&utm_medium=feed)

[Zero Heartbeat](https://hashnode.com/@clustron) · [Nov 11](https://hashnode.com/posts/per-core-licensing-for-net-server-software/6af3fbce6fbf32cc747eb43d)

### [Per-core licensing for .NET server software](https://delta1labs.hashnode.dev/per-core-licensing-for-net-server-software?utm_source=hashnode&utm_medium=feed)

Per-core licensing is how a lot of server software is sold: a price that scales with the CPU capacity the customer runs you on, because a database engine or analytics service on a 64-core box delivers

5 min read · [delta1labs.hashnode.dev](https://delta1labs.hashnode.dev/per-core-licensing-for-net-server-software?utm_source=hashnode&utm_medium=feed)

[Zero Heartbeat](https://hashnode.com/@clustron) · [Nov 10](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)
