# MonoGame + C# + content pipeline
URL: https://wwadd.dev/stacks/monogame-csharp
Last verified: 2026-09-30

A code-first 2D game workflow for .NET teams that want control of update, draw, and asset processing without an integrated scene editor.

## When to use it
- The team knows C# and wants a framework-led desktop game
- Custom game architecture and external authoring tools are acceptable
- Asset processing can be kept reproducible across builds

## How the pieces fit
MonoGame provides the game lifecycle, rendering, input, and audio. C# owns game state and systems; the content pipeline prepares assets for the runtime. Separate simulation from drawing, track asset ownership, and build content with the same toolchain in development and CI. Validate packaged builds on each desktop target. Mobile and console distribution require additional platform work; console showcase titles do not imply automatic export access.

## The tech and its role
- MonoGame: Game lifecycle, rendering, input, and audio
- Content pipeline: Asset import and build processing

## Real-world examples
- Celeste: MonoGame lists Celeste as a framework example. This establishes framework use, not its private tools or current platform porting details. (source: https://github.com/MonoGame/MonoGame)
- MonoGame samples: Official cross-platform game samples show framework usage. Learning projects rather than a production architecture template. (source: https://github.com/MonoGame/MonoGame.Samples)

## Skip if
Skip if a visual scene editor is required, browser delivery is the primary target, or a high-fidelity 3D production workflow is central.