Lesson 10: C# setup and .NET foundations: Project integration

Concept Explanation

"C# setup and .NET foundations: Project integration" brings the early basics together in one small feature instead of another isolated snippet. The aim is to show how a beginner can move from single statements to a tiny, useful flow: create data, store it, update it, and print the result in a way that feels like the start of a real app. The lesson still stays simple, but it introduces an important mindset for .NET work: even a small feature should be readable, predictable, and easy to extend.

Where to Put the Code

1. Define color and position variables at the top.
2. Create shape drawing or placement logic in the middle.
3. Render output (print, canvas, SVG, or styled block) at the end.

Command Reference

• Run the example once, then add one more task and confirm the count changes.
• Explain which line adds new data to the collection and which lines report the result.
• Change the task names so the program reads like a setup checklist you would actually use.
• Keep the example small, but treat it like the start of a real feature rather than a random print statement.

Step-by-step Guide

1. Run the starter code and read the count and latest-task output.
2. Add or rename one task so the list feels more realistic to you.
3. Explain in one sentence why a collection is more useful here than a single variable.
4. Make one focused improvement, such as clearer variable names or a cleaner output message.
5. Finish by checking that the program still runs and the displayed count matches the list contents.

Practice Exercises

• Create a similar example that stores three lesson titles instead of setup tasks.
• Extend the program so it prints every task in the list, not just the latest one.
• Build a new version that tracks completed and pending items with a simple rule.

Coding Challenges

• Turn the task-printing logic into a small method without making the example harder to follow.
• Compare storing plain strings with storing a small Task record, and explain which would scale better.

Mini Practice Tasks

• Rename one identifier so its role is obvious immediately.
• Add one more item to the list and rerun the code.
• Write one line describing what this mini feature demonstrates.