How-to guides are goal-first recipes: each one starts from a concrete intent — "I need to add a service," "I need auth," "I need this to deploy without Aspire" — and gives you the shortest reliable path from that intent to a working, verified change. They assume you already have a NetScript workspace and know the basics; they do not re-teach the framework.
If NetScript is new to you, start with the tutorials — they build one continuous application from zero. For exact API signatures, use the reference. For the concepts behind a task — why services are contracts-first, what "durable" means, how Aspire wires dependencies — read the explanation pages. Each recipe links back to the capability hub and reference that go deeper.
Build & extend a workspace
These recipes add capabilities to an existing workspace and verify the wiring.
Each lands real files under plugins/ or your service tree and ends with a
command you can run to confirm it works.
Wire primitives & observability
Recipes for the shared building blocks every plugin leans on — queues, KV, cron, and the OpenTelemetry traces that make them visible in the Aspire dashboard.
Ship the UI & deploy
Recipes for the front end and for taking a workspace to production — including the Aspire-free portability path.
How a recipe is shaped
Every how-to page follows the same contract so you always know where to look:
- Goal — one sentence stating exactly what you will have when you finish.
- Prerequisites — the workspace state and running dependencies the recipe
assumes (almost always including a live
aspire start). - Steps — added-lines code blocks, annotated with the file path they belong
in, using the public
netscript <cmd>command form throughout. - Production pitfalls — the caveats that bite in real deployments, stated plainly rather than glossed over.
- See also — the capability hub, reference page, and related recipes that take the topic further.