C# state management

Keep changing data predictable and make every screen show the current source of truth.

Chapter goal: Keep changing data predictable and make every screen show the current source of truth.

Simple explanation

State is the current memory of an app or screen. A source of truth is the one place that owns the correct current value.

In C#, this chapter is about deciding who owns changing data and who is allowed to update it. Start with the idea above. Then connect each symbol to a value or action in the example.

Do not try to remember every symbol. First ask what data the program has, what it does with that data, and what result it creates. Technical words become easier when you connect them to those three questions.

Why this topic is important

Unclear state causes stale screens, duplicated values, and changes that are difficult to trace. In C#, the syntax may look different from other languages, but the thinking skill transfers: name the data, choose the right operation, and make the next step obvious.

When to use it

Manage state for counters, forms, authentication, carts, loading, errors, filters, and cached server data.

Example code

class GameState {
  public int Score { get; private set; }
  public void AddPoints(int amount) => Score += amount;
}

var state = new GameState();
state.AddPoints(10);
Console.WriteLine(state.Score);

Line-by-line explanation

• class GameState { — This begins a class: a blueprint that groups related data and behavior.
• public int Score { get; private set; } — This line supports one focused piece of application logic. Read it together with the block directly around it.
• public void AddPoints(int amount) => Score += amount; — This stores or updates amount). The value on the right is worked out first, then saved under that name.
• var state = new GameState(); — This stores or updates state. The value on the right is worked out first, then saved under that name.
• state.AddPoints(10); — This line supports one focused piece of application logic. Read it together with the block directly around it.
• Console.WriteLine(state.Score); — This is the visible output line. It shows the final value after the earlier work is complete.

What the output means

10

The output is evidence that the program followed the instructions. If your result is different, read from the first line and write down how each value changes. That is debugging, not failure.

Mistake example

class GameState {
  public int Score { get; private set; }
  public void AddPoints(int amount) => Score += amount;
}

var state = null; // the same state is stored in more than one place
state.AddPoints(10);
Console.WriteLine(state.Score);

This version intentionally shows how the same state is stored in more than one place. The changed assignment stores a missing value, or a required line is removed, so later code cannot complete its job safely.

Fixed version

class GameState {
  public int Score { get; private set; }
  public void AddPoints(int amount) => Score += amount;
}

var state = new GameState();
state.AddPoints(10);
Console.WriteLine(state.Score);

The corrected version restores the real value or required operation. It fixes the chapter-specific problem: the same state is stored in more than one place.

Common mistakes

• Keeping the same state in several places.
• Changing state without notifying its readers.
• Using app-wide state for a value needed by one small component.

Warning: Change one part at a time. If you change many lines together, it becomes harder to learn which change caused the result.

Real use cases

• Update a Flutter widget after setState.
• Manage React state with hooks.
• Track server-owned player state safely in RedM.

Practice exercise

1. Add a reset action.
2. Keep one source of truth.
3. Explain which code owns the state and which code only reads it.

Tip: If the exercise feels too large, complete only steps 1 to 3. Small working code teaches more than a large unfinished project.

Mini quiz

1. What is a source of truth?
2. Who is allowed to change the state?
3. What causes a stale screen?

How to read AI-generated code

Do not copy AI code first. Read it like a detective. Find the data, follow the changes, and locate the final output. Ask AI to explain a line only after you have made your own guess.

• What data goes in?
• What values are stored?
• What calculation or decision happens?
• What is printed, displayed, saved, or returned?
• What can go wrong?
• Can you rename one value and still explain the code?

Language reading check

Find the program entry point, follow function calls one at a time, and keep track of each value's type. Do not jump into a class or helper until you know who calls it.

Before you move on

• I can explain this topic in my own words.
• I can read the small example without AI.
• I can change the example and predict the new result.
• I can find and fix one simple mistake.
• I can name one real project that uses this idea.

Next topic

Next, learn best practices and clean code. Before opening it, explain this chapter out loud in under one minute.